Fixes #25999: Disabling user rest API token feature from api-authorizations plugin UI #775
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
|
PR updated with a new commit |
fanf
requested changes
Dec 7, 2024
|
PR updated with a new commit |
|
PR rebased |
clarktsiory
force-pushed
the
bug_25999/disabling_user_rest_api_token_feature_from_api_authorizations_plugin_ui
branch
from
d118a08 to
9d55a88
Compare
|
This PR is not mergeable to upper versions. |
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.
https://issues.rudder.io/issues/25999
UI for the feature switch in Normation/rudder#6050 : essentially we don't display the user API token menu in the api-authorizations plugin snippet.
We still have an API endpoint to pass the configuration value, also there is some refactoring and formatting applied to the Elm code which knows about the status by calling the endpoint.
In the related PR, the user management roles and default providers are also changed, so there is some changes in the user-management plugin