[#IOPAE-175] Update RegenerateServiceKey with Manage Flow #265
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
Jira Pull Request LinkThis Pull Request refers to the following Jira issue IOPAE-175 |
balanza
approved these changes
Feb 15, 2023
Co-authored-by: Emanuele De Cupis <ema.decu@gmail.com>
|
Kudos, SonarCloud Quality Gate passed!
|
giuseppedipinto
deleted the
IOPAE-175--regenerate-service-key-manage-flow
branch
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.
Added the possibility to use MANAGE Subscription API Key as
Ocp-Apim-Subscription-Keyin RegenerateServiceKey API.In this way we are introducing the concept of MANAGE Flow for Service Management APIs.
List of Changes
Motivation and Context
Reduce User Errors with a restricted API Key scope, especially in case of Service Keys Update.
How Has This Been Tested?
Unit Tests
Screenshots (if appropriate):
Types of changes
Checklist: