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
Currently variable need to be provided either on CLI or as a file. This may be a limiting factor to the uses of this tool. I think being able to have multiple sources for variables can be very beneficial to this tool.
As an example:
Pack that defines variables A, B and C
Consul KV has key value pairs for B and C
Running the pack with variables A and B and also pointing it to Consul KV as another variable source
The output will use A and B as provided from CLI and C as available in Consul KV (B on CLI considered an override)
As an alternative -- extend templating engine to be able to query some of other Hashicorp tools for the data, such as Consul KV, Nomad Variables and Vault secrets engines.
I think this request also supersedes #409 with a bit of higher-level/wider scope.
The text was updated successfully, but these errors were encountered:
FWIW, for Consul KV I could now call consul-template to generate variable file from KV data and then use that file as an input for nomad-pack. But I think providing ability to directly externalize source of variables would play well with #472
Currently variable need to be provided either on CLI or as a file. This may be a limiting factor to the uses of this tool. I think being able to have multiple sources for variables can be very beneficial to this tool.
As an example:
As an alternative -- extend templating engine to be able to query some of other Hashicorp tools for the data, such as Consul KV, Nomad Variables and Vault secrets engines.
I think this request also supersedes #409 with a bit of higher-level/wider scope.
The text was updated successfully, but these errors were encountered: