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
If multiple stages use the same S3 bucket and events but with different prefixes, deployments, undeployments, schedules apply the S3 bucket events incorrectly.
Expected Behavior
Each stage should be capable of deploying it's own triggers and underlying only its own triggers.
Actual Behavior
The first deployment works correctly but subsequent deployments do not add the events for those stages. Undeployment of any stage deletes all events if the missing events have been added manually.
Possible Fix
During deployment or undeployment, bucket notification configurations in place as identified by trigger id should be compared to desired state (current state plus or minus event in question) and resulting configuration applied to the bucket.
Steps to Reproduce
Using zappa_settings.json below:
zappa deploy dev
Note trigger on lambda and event on S3 bucket
zappa deploy stage
Note the lack of the trigger on lambda and event on S3 bucket
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.
Originally from: Miserlou/Zappa#2111 by arcadecoffee
Context
If multiple stages use the same S3 bucket and events but with different prefixes, deployments, undeployments, schedules apply the S3 bucket events incorrectly.
Expected Behavior
Each stage should be capable of deploying it's own triggers and underlying only its own triggers.
Actual Behavior
The first deployment works correctly but subsequent deployments do not add the events for those stages. Undeployment of any stage deletes all events if the missing events have been added manually.
Possible Fix
During deployment or undeployment, bucket notification configurations in place as identified by trigger id should be compared to desired state (current state plus or minus event in question) and resulting configuration applied to the bucket.
Steps to Reproduce
Using zappa_settings.json below:
zappa deploy dev
zappa deploy stage
Your Environment
zappa_settings.json
:The text was updated successfully, but these errors were encountered: