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.

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

Identity API lambda should probably not use secrets in environment variables #223

Open
jamieparkinson opened this issue Dec 2, 2021 · 3 comments
Assignees

Comments

@jamieparkinson
Copy link
Contributor

jamieparkinson commented Dec 2, 2021

Should get them from secrets manager at runtime I think - just putting this here so I don't forget, I know @alexwlchan has views on secrets in lambdas

@cbowskill cbowskill removed the status in Digital experience Mar 16, 2022
@cbowskill cbowskill moved this to Sprint backlog in Digital experience Mar 16, 2022
@jamieparkinson jamieparkinson moved this from Sprint backlog to In progress in Digital experience Mar 17, 2022
@jamieparkinson jamieparkinson self-assigned this Mar 17, 2022
@jamieparkinson jamieparkinson moved this from In progress to Blocked in Digital experience Mar 24, 2022
@jamieparkinson
Copy link
Contributor Author

@pollecuttn
Copy link

@jamieparkinson does this still need to be open and in the blocked column on the digital access board?

@jamieparkinson
Copy link
Contributor Author

Open, yes, blocked no - should be moved to the backlog

@jamieparkinson jamieparkinson moved this from Blocked to Backlog in Digital experience Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants