Per discussion, would like the ability to render .j2 or .conf files stored under the k8s directory but not deploy them.
Use case: configurations may change between dev through prod deployments. We want to be able to create configuration (in this case consul) which is abstract enough to be checked in and rendered as part of the deployment in different environments.
For now, I can handle the deployment of the configs into the cluster (i.e. consul). In the far future, perhaps forge will do this automatically - a interface layer to a partner as they do with deploys to kubernetes.
Per discussion, would like the ability to render .j2 or .conf files stored under the k8s directory but not deploy them.
Use case: configurations may change between dev through prod deployments. We want to be able to create configuration (in this case consul) which is abstract enough to be checked in and rendered as part of the deployment in different environments.
For now, I can handle the deployment of the configs into the cluster (i.e. consul). In the far future, perhaps forge will do this automatically - a interface layer to a partner as they do with deploys to kubernetes.