test: add test env var to section mgr lambda to debug missing env var #286
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.
Goal
the pre-existing
JWT_KEY
env var (line 48 in the file changed) was never created in prod. hypothesis is theignoreEnvironmentVars: ['GIT_SHA']
line is buggy, and preventing environment vars from getting deployed.steps taken here (copied from jira):
submitted a PR with a new env var added (
TEST: 'test'
). infrastructure plan showed no changes to the lambda, and a deploy to dev did not add theTEST
env var.added a commit to the PR commenting out this line: ignoreEnvironmentVars: ['GIT_SHA']. this time, the infrastructure plan showed changes, including adding the
TEST
env var.changed PR to only remove the
ignoreEnvironmentVars
directive and deployed to dev. even though theGIT_SHA
was shown to be changed tonull
in the plan, it showed up in the lambda as the latest/correct commit hash. (this must be being pulled in elsewhere?)References
JIRA ticket: