Enable user to configure custom Access/Refresh token #5087
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
fguimond
reviewed
Feb 13, 2025
CHANGELOG-6.md
Outdated
| @@ -5,6 +5,11 @@ All notable changes to this project will be documented in this file. | |||
| The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) | |||
| and this project adheres to [Semantic | |||
| Versioning](http://semver.org/spec/v2.0.0.html). | |||
| ## [6.12.1] - Unreleased | |||
There was a problem hiding this comment.
As discussed let's make this 6.13.0.
There was a problem hiding this comment.
Changed to full release instead of patch release
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.
What is this change?
Allow users to change Access/Refresh token expiry
Why is this change necessary?
Sensu-go users requirement
Does your change need a Changelog entry?
Changelog updated
Do you need clarification on anything?
No
Were there any complications while making this change?
No
Have you reviewed and updated the documentation for this change? Is new documentation required?
Documentation required
How did you verify this change?
Manual testing
Is this change a patch?
NO