add a flag to ssm variables to resolve as string instead of object #1
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.
A PR to serverless https://github.com/serverless/serverless/pull/5842/files changed how ssm variables were resolved for secrets manager. If the content of the secret was a valid JSON string, then it was parsed and returned as a JSON object. This causes issues when trying to use the secret in an environment variable.
This PR extends the extended syntax for ssm variables to add a directive
decryptAsPlaintext
to skip the json parsing so that the plain text value is returned.This branch was created from tag 1.51.0. (as that is the version we were using at the time).
TODO:
What did you implement
Closes #XXXXX
How can we verify it
Todos
Useful Scripts
npm run test:ci
--> Run all validation checks on proposed changesnpm run lint:updated
--> Lint all the updated filesnpm run lint:fix
--> Automatically fix lint problems (if possible)npm run prettier-check:updated
--> Check if updated files adhere to Prettier confignpm run prettify:updated
--> Prettify all the updated filesIs this ready for review?: NO
Is it a breaking change?: NO