generated from cloudoperators/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(cluster) configurable max token validity (#518) #634
Merged
gciezkowski-acc
merged 20 commits into
main
from
feat/518_configurable_max_token_validity
Oct 29, 2024
Merged
feat(cluster) configurable max token validity (#518) #634
gciezkowski-acc
merged 20 commits into
main
from
feat/518_configurable_max_token_validity
Oct 29, 2024
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
github-actions
bot
added
documentation
Improvements or additions to documentation
feature
core-apis
labels
Oct 10, 2024
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
10 times, most recently
from
October 16, 2024 12:51
9ed7021
to
3ebd585
Compare
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
2 times, most recently
from
October 16, 2024 14:00
d6e2dc4
to
f4b0b36
Compare
IvoGoman
reviewed
Oct 18, 2024
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
from
October 21, 2024 09:50
202a624
to
026e021
Compare
kengou
requested changes
Oct 21, 2024
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
2 times, most recently
from
October 22, 2024 11:58
9440db8
to
c742bea
Compare
IvoGoman
reviewed
Oct 23, 2024
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
2 times, most recently
from
October 24, 2024 08:22
4c1fdee
to
1abe7ca
Compare
IvoGoman
reviewed
Oct 25, 2024
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
from
October 28, 2024 09:32
bfb1d5b
to
67c2565
Compare
IvoGoman
approved these changes
Oct 28, 2024
This reverts commit 585f2dc.
gciezkowski-acc
force-pushed
the
feat/518_configurable_max_token_validity
branch
from
October 28, 2024 15:04
da30350
to
aad9425
Compare
kengou
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Description
I added the configurable parameter max token validity to the cluster specification, ensuring it does not negatively impact existing clusters.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist