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

[Core feature] Event Based Sensors for bucket upload events #4679

Open
2 tasks done
ajbeach2 opened this issue Jan 4, 2024 · 1 comment
Open
2 tasks done

[Core feature] Event Based Sensors for bucket upload events #4679

ajbeach2 opened this issue Jan 4, 2024 · 1 comment
Labels
enhancement New feature or request epic feature-request flytekit FlyteKit Python related issue pri1

Comments

@ajbeach2
Copy link

ajbeach2 commented Jan 4, 2024

Motivation: Why do you think this is important?

Processing files uploaded to GCS buckets and triggering processing based on the prefix is a common pattern. Different prefixs may trigger different workflows.

Right now, the FileSensor supports bucket keys, but not prefixes.

This use case is more generically a Pub/Sub sensor because typically you would configure the bucket to send a notification to a PubSub Topic based on the prefix.

Goal: What should the final outcome look like, ideally?

This feature would allow for triggering workflows from pub/sub topics. With this feature, it would be possible to setup workflows to be triggered by events from different prefixes in GCS buckets.

Describe alternatives you've considered

This use case can be satisfied by a custom Sensor class, or by having an external service that subscribes or polls events which triggers the workflows programmatically. These solutions are less convenient.

Propose: Link/Inline OR Additional context

The proposed solution is to create an PubSubSensor. There could also be an SQS or SNS sensor to support S3/AWS. A more generic class to support multiple topic/queue types my also be considered.

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@ajbeach2 ajbeach2 added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Jan 4, 2024
Copy link

welcome bot commented Jan 4, 2024

Thank you for opening your first issue here! 🛠

@pingsutw pingsutw added flytekit FlyteKit Python related issue pri1 feature-request epic and removed untriaged This issues has not yet been looked at by the Maintainers labels Jan 4, 2024
@flyteorg flyteorg deleted a comment from dosubot bot Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request epic feature-request flytekit FlyteKit Python related issue pri1
Projects
None yet
Development

No branches or pull requests

2 participants