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

Are global bucket names an issue? #29

Closed
Tracked by #5
matweldon opened this issue Mar 27, 2024 · 1 comment
Closed
Tracked by #5

Are global bucket names an issue? #29

matweldon opened this issue Mar 27, 2024 · 1 comment

Comments

@matweldon
Copy link
Collaborator

Users will create buckets for each party called f"{party_name}-bucket"

We're relying a lot on users being creative at naming buckets.

Is there some way we could generate a short hash which is generated (for example) the first time they run scripts/01... for each party, but is not regenerated if they run the script again. Then use that hash in the bucket name?

@matweldon matweldon mentioned this issue Mar 27, 2024
4 tasks
@daffidwilde
Copy link
Contributor

I suppose we could do something like hash the .env file, but then what if the same group of users wanted to do another linkage project? They'd have to come up with different names for their projects, I guess.

I still think it's easier for everyone if we tell users to decide on a hash before starting and use that to name their projects. Happy to keep discussing this though!

@matweldon matweldon closed this as not planned Won't fix, can't repro, duplicate, stale Apr 3, 2024
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

No branches or pull requests

2 participants