Closed mattk42 closed 8 years ago
To add some color on implementation details, one of the two things will need to happen to make this work:
I'm pretty sure we already do this and have been doing so since 2014. Is this untrue in master?
yes..whatever is set via deis config:set <>
should be available to the build environment
It certainly works fine for me. I use a custom buildpack that references environment variables at compile time to generate an nginx config.
Awesome! Sorry for the confusion, I'll go ahead and close this.
Both V1 and Heroku support passing config as env vars to the builders, but this is currently missing in workflow. I would like to see this personally as some of my builds rely on specific env vars set to authenticate with external private ruby gem repositories.