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
There can be many instances of CloudFunctionConfiguration in the xml response, but only one is parsed into a python dict. Looks to be a problem in botocore schema?
The text was updated successfully, but these errors were encountered:
You'll need to use get_bucket_notification_configuration instead. The docs mention that this is deprecated in favor of get_bucket_notification_configuration.
The history on why we have both methods is that we realized that get_bucket_notification was modeled incorrectly, and as you mention, we were only parsing one element because we didn't model this value as a list.
The problem we ran into was that we could not modify this in a backwards compatible way (for users that only have one configuration and are using the dictionary without issues). Because of this, we decided to create a new method, get_bucket_notification_configuration which was the "correctly modeled" version of this operation and deprecated the old method.
In some future major version of the SDK (way, way in the future) we'll probably remove get_bucket_notification, but for now, we support both methods.
There can be many instances of CloudFunctionConfiguration in the xml response, but only one is parsed into a python dict. Looks to be a problem in botocore schema?
The text was updated successfully, but these errors were encountered: