Is there a practical way to use a remote file as a jinja template in template modules ?
Let’s explain my use case:
My application code requires configuration that may vary depending on the environment (dev/staging/prot)
I want to keep configuration defintion into application code, as j2 template, because it’s easier to maintain.
Those templates are deployed on the target machines along with the app, and then ansible creates final configuration files, using host/group variables.
My application code requires configuration that may vary depending on the
environment (dev/staging/prot)
I want to keep configuration defintion into application code, as j2
template, because it's easier to maintain.
Those templates are deployed on the target machines along with the app,
and then ansible creates final configuration files, using host/group
variables.
Fun pattern; I'd be curious what your final implementation is for this. My
first inclination is that of "just centralize it in the repo- say via git
submodules", but that has it's own issues.