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

Feature Request: Support lock destination path #12

Open
laferrieren opened this issue Sep 23, 2020 · 3 comments
Open

Feature Request: Support lock destination path #12

laferrieren opened this issue Sep 23, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@laferrieren
Copy link

When we create a bucket via the operator, there isn't a way to lock the destination path. For a lot of our workloads the path we are outputting to matters and should static. We end up need to go into the UI and toggling the Lock destination path options for the destination configurations for a bucket for the vast majority of our buckets. Every time the operator recreates the bucket we need to go back into the UI and manually set that setting. It would a significant improvement if we could lock the path in the CRD.

@rusenask
Copy link
Member

Hi, thanks for raising the issue, definitely makes sense to add it

@rusenask rusenask self-assigned this Sep 23, 2020
@rusenask rusenask added the enhancement New feature or request label Sep 23, 2020
@rusenask
Copy link
Member

rusenask commented Sep 23, 2020

@laferrieren should be fixed in #14 (actual implementation was in #13)

@laferrieren
Copy link
Author

@laferrieren should be fixed in #14 (actual implementation was in #13)

Thanks, this is awesome! Amazing turn around, look forward to rolling it later this week.

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

No branches or pull requests

2 participants