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

Allow regex in SOURCE_BUCKETS for environment variable #138

Closed
wants to merge 1 commit into from
Closed

Allow regex in SOURCE_BUCKETS for environment variable #138

wants to merge 1 commit into from

Conversation

harriswong
Copy link

@harriswong harriswong commented Jul 29, 2019

Issue #, if available:
#141

Description of changes:
This allow us to support regex in SOURCE_BUCKETS for the environment variable so that it matches a regex of bucket instead of CSV buckets.

Environment variable has limited string limit and doesn't allow us to enter a long list of buckets. (Imagine 50+ devs and each has their own bucket). Using regex won't have this character limit problem and is better for scaling.

I created a PR to demonstrate the idea of using regex in the field. It defaults to use sourceBuckets[0]. Improvement and feedback are welcome.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This allow us to support regex in SOURCE_BUCKETS for the environment
variable so that it matches a regex of bucket instead of CSV buckets.

CSV has a limited string limit and doesn't allow user to enter a long
list of buckets.
@hayesry
Copy link
Member

hayesry commented Aug 3, 2019

Hey @harriswong thanks for creating this pull request. I've added this for review into our next minor version release!

@powertoaster
Copy link

This would be a huge improvement for me as well. I need to support a large number of buckets that could easily be defined via a REGEX.

@beomseoklee
Copy link
Member

Thanks for your effort here, @harriswong
We have updated our solution, and your pull request has been merged into our master branch. However, as we've merged many pull requests at this time, the source code might not exactly same as what you've done. In addition, due to our internal process, we've merged source code manually, so please understand how your effort has been merged.

You can refer to the recent changes here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants