-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Lambda Blob format incorrect #22
Comments
Paging @pimterry |
Totally makes sense to me. The backing AWS data for this is here, and the conversion logic is over here. Right now, it:
I think we should treat blob as a special case here, which is always in It doesn't sound like this is an urgent problem for now, and I'm quite busy, so I'm not going to be able to fix this in the short term. Assuming @MikeRalphson agrees with the plan above though, it should be easy to put in a PR for the linked aws2openapi conversion logic to add that special case, and fix this. |
The
Blob
definition is defined here. ABlob
is used in a few locations, one of which is in a Code object here. According to the AWS API Reference doc, this should be encoded as "Base64-encoded binary data object." Swagger has support for Base64 encoded content by using theformat: byte
property. TheBlob
format
property is currently set topassword
. I believe it should be set tobyte
.The text was updated successfully, but these errors were encountered: