fix: allow apiKeyAuthorizationMode to be undefined if defaultAuthorizationMode is apiKey #2329
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.
Problem
If
defaultAuthorizationMode
is set to"apiKey"
andapiKeyAuthorizationMode
is not defined the deploy will fail with an error. On the data construct sideapiKeyConfig
is required ifdefaultAuthorizationMode
isAPI_KEY
. TheconvertAuthorizationModesToCDK
should provideapiKeyConfig
in this case.Issue number, if available: aws-amplify/amplify-category-api#2994
Changes
Allow
apiKeyAuthorizationMode
to be undefined ifdefaultAuthorizationMode
is"apiKey"
.Corresponding docs PR, if applicable:
Validation
Checklist
run-e2e
label set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.