You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.
AWS Transfer Family supports a list of protocols. These are defined as strings, and can be: "SFTP", "FTP", "FTPS" and "AS2". An example from the Cloudformation resource manual page:
"Protocols": ["SFTP"],
The goformation schema defines AWS::Transfer::Server.Protocols as an array of AWS::Transfer::Server.Protocol objects.
This causes schema linting to fail, because they expect an object where "SFTP" is now passed.
I believe the solution would be to remove Server.Protocol completely and replace the definition with an enum... but I have no experience with this repo, and no clue how the code generator that spits out the schema actually works.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AWS Transfer Family supports a list of protocols. These are defined as strings, and can be: "SFTP", "FTP", "FTPS" and "AS2". An example from the Cloudformation resource manual page:
The goformation schema defines AWS::Transfer::Server.Protocols as an array of
AWS::Transfer::Server.Protocol
objects.which in turn are defined as simple
object
s.This causes schema linting to fail, because they expect an object where "SFTP" is now passed.
I believe the solution would be to remove Server.Protocol completely and replace the definition with an enum... but I have no experience with this repo, and no clue how the code generator that spits out the schema actually works.
The text was updated successfully, but these errors were encountered: