Skip to content
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

notifications are getting appended to the getbucket-notification configuration #8758

Closed
ramya-c3 opened this issue Feb 4, 2025 · 1 comment
Assignees
Labels

Comments

@ramya-c3
Copy link

ramya-c3 commented Feb 4, 2025

Environment info

  • NooBaa Version: noobaa-core-5.18.0-20250201.el9.x86_64
  • Platform: standalone

Actual behavior

1.]# alias s3cp1='AWS_ACCESS_KEY_ID=sdf AWS_SECRET_ACCESS_KEY=fd/3euGoVsKfe7+SGWR aws --endpoint http://1.1.1.1:6001'
[root@ramyac-scale-host ~]# 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:
"
]
}
]
}
[root@ramyac-scale-host ~]# vi notification.json
[root@ramyac-scale-host ~]# cat notification.json
{
"TopicConfigurations": [
{
"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

@alphaprinz
Copy link
Contributor

5.18 PR #8763

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants