fix: ACNA-1756 - config schema changes for integration type apikey #568
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
Issue:
Expected Behaviour
Actual Behaviour
Implementation:
New response will not have
oauth2
object block forintegration_type = apiKey
incredentials
arrayInstead, it will have
apikey = client_id_val
directly in the schemaNew response
Related Issue
ACNA-1756
Motivation and Context
This is a very critical bugfix to patch breaking app dev
How Has This Been Tested?
aio-cli
Screenshots (if appropriate):
Types of changes
Checklist: