We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the different notifications are applied for same bucket instead of replacing it is appending
{ "TopicConfigurations": [ { "Id": "notify_event", "TopicArn": "connection.json", "Events": [ "s3:ObjectCreated:" ] }, { "Id": "notify_event", "TopicArn": "connection.json", "Events": [ "s3:ObjectCreated:" ] } ] }
{ "TopicConfigurations": [ { "Id": "notify_event", "TopicArn": "connection5.json", "Events": [ "s3:ObjectCreated:" ] }, { "Id": "notify_event", "TopicArn": "connection.json", "Events": [ "s3:ObjectCreated:" ] } ] }
1.only one connection should be present
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment info
Actual behavior
When the different notifications are applied for same bucket instead of replacing it is appending
s3cp1 s3api put-bucket-notification-configuration --bucket scenario1bucket1 --notification-configuration file://notification.json
s3cp1 s3api get-bucket-notification-configuration --bucket scenario1bucket1
{
"TopicConfigurations": [
{
"Id": "notify_event",
"TopicArn": "connection.json",
"Events": [
"s3:ObjectCreated:"
]
},
{
"Id": "notify_event",
"TopicArn": "connection.json",
"Events": [
"s3:ObjectCreated:"
]
}
]
}
cat notification5.json
{
"TopicConfigurations": [
{
"Id": "notify_event",
"TopicArn": "connection5.json",
"Events": [
"s3:ObjectCreated:"
]
},
{
"Id": "notify_event",
"TopicArn": "connection.json",
"Events": [
"s3:ObjectCreated:"
]
}
]
}
Expected behavior
1.only one connection should be present
Steps to reproduce
More information - Screenshots / Logs / Other output
The text was updated successfully, but these errors were encountered: