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
Support safely re-rendering templates, meaning if an exception is thrown during render, don't overwrite the previously rendered template.
Example situation:
You have a Rails database.yml file being rendered by Consult.
In production, your application boots successfully, rendering database.yml.
The next process that boots throws an exception for whatever reason, and the app fails to launch as a result
Instead of the app failing to launch, we should allow for graceful (and reported - meaning, the error makes it to Rollbar or whatever) failure, so the app can boot with the previously rendered template.
Questions:
Should this be configurable on a per-template basis?
Should this be the default behavior?
The text was updated successfully, but these errors were encountered:
Support safely re-rendering templates, meaning if an exception is thrown during render, don't overwrite the previously rendered template.
Example situation:
database.yml
file being rendered by Consult.database.yml
.Instead of the app failing to launch, we should allow for graceful (and reported - meaning, the error makes it to Rollbar or whatever) failure, so the app can boot with the previously rendered template.
Questions:
The text was updated successfully, but these errors were encountered: