Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Figure out and fix "Problem accessing SSM parameters" on PROD runs #109

Open
mathomas opened this issue Jul 19, 2018 · 0 comments
Open

Figure out and fix "Problem accessing SSM parameters" on PROD runs #109

mathomas opened this issue Jul 19, 2018 · 0 comments
Projects
slink-board

Comments

@mathomas
Copy link
Contributor

mathomas commented Jul 19, 2018 •
edited

We get this exception every production run, but then it continues to operate normally. Should be fixed, since it's a false alarm.

2018-07-12T19:55:15.640Z	7e7abd67-860d-11e8-872e-a1cab863f08b	Problem accessing SSM parameters for /slink/PROD Error: Configuration value not found in SSM Parameter Store for: /slink/PROD/undefined
at keys.forEach (/var/task/config.js:90:15)
at Array.forEach (<anonymous>)
at Object.loadConfigParams (/var/task/config.js:83:10)
at <anonymous>
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
@mathomas mathomas created this issue from a note in slink-board (To do) Jul 19, 2018
@mathomas mathomas changed the title Figure out and fix problem reading production configuration. Figure out and fix "Problem accessing SSM parameters" on PROD runs Jul 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
slink-board
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mathomas