-
Notifications
You must be signed in to change notification settings - Fork 152
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
Generate credentials file at startup, not build time #1
Conversation
The config var value can be changed at any moment, and doing so shouldn't require a new deployment. Generating this file at build time also means it's not possible to use Heroku Pipelines, as a promotion doesn't trigger a new deployment.
Hey dmathieu can you tell me if I have to change the |
The echo won't be displayed. It's sent to the For reference, here is the doc on profile.d scripts: https://devcenter.heroku.com/articles/buildpack-api#profile-d-scripts |
Thank you @marcmetz. I've added escaping of the content. cedar-14 is already deprecated anyway, and heroku-16 will be in april. |
@marcmetz are you able to use heroku-18 stack and test this out? |
I just tested it. It works. Thank you! |
The config var value can be changed at any moment, and doing so
shouldn't require a new deployment.
Generating this file at build time also means it's not possible to use
Heroku Pipelines, as a promotion doesn't trigger a new deployment.