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
Hello,
I have a feature request and wondering if it's worth implementing or not. Essentially, I have a folder containing a bunch of configuration files and templates e.g. CloudWatch configs, Dockerfiles etc. Like so:
I'm using p2's --directory-mode to render templates, and the templates have a .p2 suffix which is removed by using the --directory-mode-filename-substr-del flag.
In the (highly) unlikely event that one of my non-template configuration files (e.g. Dockerfile in the example above) has p2-recognisable syntax, then p2 will attempt to render that file as a template. I was wondering if it's worth adding a filter to only render files that have the .p2 suffix.
The text was updated successfully, but these errors were encountered:
Hello,
I have a feature request and wondering if it's worth implementing or not. Essentially, I have a folder containing a bunch of configuration files and templates e.g. CloudWatch configs, Dockerfiles etc. Like so:
I'm using p2's
--directory-mode
to render templates, and the templates have a.p2
suffix which is removed by using the--directory-mode-filename-substr-del
flag.In the (highly) unlikely event that one of my non-template configuration files (e.g. Dockerfile in the example above) has p2-recognisable syntax, then p2 will attempt to render that file as a template. I was wondering if it's worth adding a filter to only render files that have the
.p2
suffix.The text was updated successfully, but these errors were encountered: