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.

Sign up for GitHub

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

Jump to bottom

Lock the keystone resources after a deployment #321

Open
berendt opened this issue Sep 23, 2022 · 0 comments
Open

Lock the keystone resources after a deployment #321

berendt opened this issue Sep 23, 2022 · 0 comments
Labels
enhancement New feature or request upstream Implemented directly in the upstream

Comments

@berendt
Copy link
Member

berendt commented Sep 23, 2022 •
edited
Loading

It is possible to lock keystone resources. This should be done after a deployment or before an upgrade. This way it can be ensured that e.g. the service project cannot be removed or that endpoints are not modified because of wrong configuration settings.
@berendt berendt added enhancement New feature or request upstream Implemented directly in the upstream labels Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request upstream Implemented directly in the upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@berendt