complement credential handling of official compliance check pipeline #347
+8
−2
Conversation
This file contains hidden or 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: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
depressiveRobot
added
the
documentation
mbuechse
reviewed
Jan 22, 2026
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Co-authored-by: Matthias Büchse <matthias.buechse@alasca.cloud> Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
Contributor
|
@depressiveRobot Actually, I'm not sure the admonition is being rendered correctly, but this may be a problem on Github only. I hope it will be fine on the actual docs page. |
Contributor
Author
|
With the local development server it renders fine ( |
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.
Improves the documentation regarding the handling of application credentials when using the official compliance check pipeline. It is now explicitly stated that operators themselves are responsible for expiring credentials.
See SovereignCloudStack/standards#1046