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
we are considering using gomplate for rendering configurations for infrastructure rollouts (e.g. outputting terraform files).
As we want to support the full lifecycle of such components, it would also be handy if gomplate was able to just delete the output files of a templating step, especially as we are using outputMap and the actual output path for the input templates is different based on the datasources and the target folder potentially also consists of other files.
From our side two options could really help here:
Adding a --delete option to the CLI so that gomplate is deleting the output files instead of rendering
Adding something like a --dry-run option which prints the paths of all files which would be rendered
Would you consider adding one of those options to gomplate?
The text was updated successfully, but these errors were encountered:
mihkels
added a commit
to mihkels/gomplate
that referenced
this issue
Jan 16, 2025
Hi,
we are considering using gomplate for rendering configurations for infrastructure rollouts (e.g. outputting terraform files).
As we want to support the full lifecycle of such components, it would also be handy if gomplate was able to just delete the output files of a templating step, especially as we are using outputMap and the actual output path for the input templates is different based on the datasources and the target folder potentially also consists of other files.
From our side two options could really help here:
Would you consider adding one of those options to gomplate?
The text was updated successfully, but these errors were encountered: