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

[Migrated] Scheduling event on s3 bucket fails #545

Closed
jneves opened this issue Feb 20, 2021 · 2 comments
Closed

[Migrated] Scheduling event on s3 bucket fails #545

jneves opened this issue Feb 20, 2021 · 2 comments
Labels
auto-closed [Bot] Closed, details in comments aws no-activity [Bot] Closing soon if no new activity

Comments

@jneves
Copy link
Contributor

jneves commented Feb 20, 2021

Originally from: Miserlou/Zappa#1442 by jesse-peters

Context

Using zappa on python 3.6 inside a venv.

Expected Behavior

I have an s3 bucket which has a few existing event subscriptions. There is no overlap with the event subscription that zappa is trying to manage. I expect to be able to schedule a new subscription with zappa, even if there are already some on the bucket.

Actual Behavior

It looks at the bucket, and says that the event schedule already exists.

Possible Fix

I suspect it is only looking at the event types, and does not actually look at the filters when looking to see if an s3 event subscription already exists.

Steps to Reproduce

  1. Add an event subscription on prefix A manually to an s3 bucket
  2. Attempt to schedule zappa with an event subscription on prefix B. It should tell you that the event subscription already exists.

Your Environment

  • Zappa version used: 0.45.1
  • Your zappa_settings.py:
{
			"function": "app.function",
			"event_source": {
				"arn": "arn:aws:s3:::s3bucketname",
				"key_filters": [{
					"type": "prefix",
					"value": "A"
				}],
				"events": [
					"s3:ObjectCreated:*"
				]
}
Copy link

github-actions bot commented Apr 3, 2024

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.

@github-actions github-actions bot added the no-activity [Bot] Closing soon if no new activity label Apr 3, 2024
Copy link

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.

@github-actions github-actions bot added the auto-closed [Bot] Closed, details in comments label Apr 13, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-closed [Bot] Closed, details in comments aws no-activity [Bot] Closing soon if no new activity
Projects
None yet
Development

No branches or pull requests

1 participant