Update Domain Manager instructions to reflect latest changes #238
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Markus Hentsch <[email protected]>
|
Marking as Draft, depends on SovereignCloudStack/standards#586 |
|
This depends on the Keystone 2023.1. I edited the PR description to reflect that. We should make sure that SCS demands at least that version before merging this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with OpenStack Keystone 2023.11, the exposure of all domains to domain managers is fixed.
As soon as we can make sure that this release is a minimum requirement for SCS, the corresponding remarks can be removed from the documentation.
Footnotes
https://bugs.launchpad.net/keystone/+bug/2041611 ↩