-
|
Other operations may also be affected. Is it intentional? Why? |
Beta Was this translation helpful? Give feedback.
Answered by
Velfi
Apr 10, 2023
Replies: 2 comments
-
|
The field becoming non-optional was unintentional. We do plan to make required response fields non-optional in the future, but we're not ready yet. This was caused by a bug in codegen related to the smithy model for S3. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Velfi
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The field becoming non-optional was unintentional. We do plan to make required response fields non-optional in the future, but we're not ready yet. This was caused by a bug in codegen related to the smithy model for S3.