Fix double quote escaping in OKTA secrets creation script #177
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 does this PR do?
Fixes the OKTA secrets creation script to properly handle environment variables that contain values wrapped in double quotes.
Motivation
When users set OKTA environment variables with quoted values (e.g.,
OKTA_CLIENT_ID="value"
), the script generates malformed JSON with double-escaped quotes, causing ECS tasks to fail during secret retrieval.Fixes #176
Changes
For Moderators
Additional Notes
This fix specifically addresses the OKTA section where the issue was reported. The fix has been tested with both quoted and unquoted environment variable values.