Do not rebuild when changing environment variables (cache container builds)
planned
J
Jaap Frolich
Just use the previously build container image. Even better would be to cache the git ref, so even if the same ref is being published to a new branch (perhaps staging => production) it will be a fast deploy.
Log In
J
John Ruble
This should probably be combined with better visibility and control over which env vars are available at _build time_. Maybe when you add an env var to render, you have to say whether to make it available at build-time, runtime, or both?
(then Render would be able to know whether an env var change invalidates a build, and that the build can be safely reused)
Anurag Goel
planned
M
Michael Hellein
This is absolutely a necessity for operating production services. Needing to wait through a build (which may include an unknown amount of waiting in Render's build infrastructure queues) to make an environment change doesn't make any sense - we are not changing the deployed code, we are changing its environment!
B
Ben Lopatin
This capability (or lack thereof) is a hard blocker to even considering migrating any customer facing services to Render. Whether its a new connection string, API key, or fixing a typo in variable, waiting for a complete build is a non-starter.