You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, to support password-protected demos, we need to use our Heroku instances, because:
developers have to set BASIC_AUTH_CREDS="username:password" as an env var, but because those need to be committed to get them only Cloud Run, it's not viable to commit them to the public repo
Secrets are shared across all Cloud Run demo services, so if set BASIC_AUTH_CREDS in Secrets, they'd apply to all demos
So, obvs, we need a solution - and one that ideally is very light touch
The text was updated successfully, but these errors were encountered:
One option might be to stably generate random-but-readable passwords using the branch name as a seed then log them out to the private logs for a developer to pick up and share as needed. The credentials would be different per branch name, but not change with each commit to that branch
At the moment, to support password-protected demos, we need to use our Heroku instances, because:
So, obvs, we need a solution - and one that ideally is very light touch
The text was updated successfully, but these errors were encountered: