Closed Sam152 closed 6 months ago
Here's the related code where zappa schedules events: https://github.com/zappa/Zappa/blob/master/zappa/core.py#L2775
zappa uses kappa to update the s3 event source.
I suspect the unschedule remove()
action may be removing the notification configuration.
However, I wonder if this is just a cosmetic issue on aws's side.
I have seen issues with triggers defined by zappa or cfn files that don't show in the console, but function as expected.
Do S3 notifications still work with the target bucket?
Not in this case, no. Once the EventBridge integration reflects as "Off" in the UI, events are no longer delivered to EventBridge.
Revisiting this, I haven't tested it, but I also wonder if other "Event notifications" would also be removed when deploying a zappa project.
The easiest workaround we could implement in zappa is to provide a flag to ignore redeploying events.
In your case, I would use zappa for packaging and separate deployment.
I'd like to see a point where zappa has a more clearly separated deployment/packaging integration, where zappa generates the cloudformation templates that you could edit if necessary, then the zappa deployment commands just wrap the related cloudformation calls.
Hi there! Unfortunately, this Issue has not seen any activity for at least 90 days. If the Issue is still relevant to the latest version of Zappa, please comment within the next 10 days if you wish to keep it open. Otherwise, it will be automatically closed.
Hi there! Unfortunately, this Issue was automatically closed as it had not seen any activity in at least 100 days. If the Issue is still relevant to the latest version of Zappa, please open a new Issue.
This is still an issue
Context
Expected Behavior
Actual Behavior
Possible Fix
Steps to Reproduce
Create a project with the following configuration:
Enable EventBridge integration for the bucket: