As best we can tell the best-practice way to have Terraform manage Consul manage/configured services, is with the Nomad
template stanza, and the Terraform Nomad provider resources.
If our guess is correct, Consul service configuration files are best deployed and managed in production via a Nomad
template. In turn the Nomad job state is managed via Terraform.
This lead us to wonder what, if any, are the functional differences between Consul-Template and Nomad
template stanzas. We can see from the docs that Nomad
template uses Consul-Template. However it is quite a leap of faith to assume that Nomad
template exposes all the functionality of Consul-Template. In fact if it did we’d expect a statement to that effect. If we’ve missed/overlooked that statement - apologies - but please point it out.
template exposes only a subset of Consul-Template functionality:
Does any one know of a feature/function comparison table for these two?