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

put-bucket notification should check the connection before saving the information to the bucket #8649

Open
ramya-c3 opened this issue Jan 6, 2025 · 0 comments
Labels

Comments

@ramya-c3
Copy link

ramya-c3 commented Jan 6, 2025

Environment info

  • NooBaa Version 5.18.0-20250101
  • Platform: standalone

Actual behavior

cat connection1.json

{
        "agent_request_object": {"host": "ramyamc-24.vmlocal", "port": 9001, "timeout": 100},
        "request_options_object": {"auth": "root:Cluster4scale","path": "/webhook"},
        "notification_protocol": "http",
        "name": "notify_event1"
}
 
#cat notification.json
 
{
  "TopicConfigurations": [
    {
      "Id": "notify_event",
      "TopicArn": "connection10.json",
      "Events": [
        "s3:ObjectCreated:*"
      ]
    }
}

I have placed wrong json

now i try to

s3cp1 s3api put-bucket-notification-configuration --bucket bucket123 --notification-configuration file://notification.

s3cp1 s3api get-bucket-notification-configuration --bucket bucket123

{
"TopicConfigurations": [
{
"Id": "notify_event",
"TopicArn": "connection10.json",
"Events": [
"s3:ObjectRemoved:*"
]
}
]
}

it fails when i try to do noobaa-cli notification

Expected behavior

  1. it should fail in this call
    s3cp1 s3api put-bucket-notification-configuration --bucket bucket123 --notification-configuration file://notification.

Steps to reproduce

More information - Screenshots / Logs / Other output

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

1 participant