-
Notifications
You must be signed in to change notification settings - Fork 221
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
Make aws.api#unsignedPayload trait an annotation trait #232
Labels
breaking-change
This issue requires a breaking change to remediate.
Comments
mtdowling
added a commit
that referenced
this issue
Jan 28, 2020
The aws.api#unsignedPayload trait currently takes a set of signing names to enable unsigned payloads on. However, I don't think we will ever need this level of granularity and it makes it more difficult to implement codegen. Closes #232
mtdowling
added a commit
that referenced
this issue
Feb 5, 2020
The aws.api#unsignedPayload trait currently takes a set of signing names to enable unsigned payloads on. However, I don't think we will ever need this level of granularity and it makes it more difficult to implement codegen. Closes #232
JordonPhillips
pushed a commit
to JordonPhillips/smithy
that referenced
this issue
Mar 5, 2020
The aws.api#unsignedPayload trait currently takes a set of signing names to enable unsigned payloads on. However, I don't think we will ever need this level of granularity and it makes it more difficult to implement codegen. Closes smithy-lang#232
mtdowling
added a commit
that referenced
this issue
Mar 16, 2020
The aws.api#unsignedPayload trait currently takes a set of signing names to enable unsigned payloads on. However, I don't think we will ever need this level of granularity and it makes it more difficult to implement codegen. Closes #232
JordonPhillips
pushed a commit
to JordonPhillips/smithy
that referenced
this issue
Apr 22, 2020
The aws.api#unsignedPayload trait currently takes a set of signing names to enable unsigned payloads on. However, I don't think we will ever need this level of granularity and it makes it more difficult to implement codegen. Closes smithy-lang#232
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
aws.api#unsignedPayload
trait currently takes a set of signing names to enable unsigned payloads on. However, I don't think we will ever need this level of granularity and it makes it more difficult to implement codegen.The text was updated successfully, but these errors were encountered: