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
Update the first template content to "hello, {{ key \"hello\" }}"
Send SIGHUP signal to reload config/template
ID for the first template is different
Expected behavior
Consistent identifier for a template even upon changes to its content.
This is not a bug, and the template IDs changing are expected on reload since the identifier of templates are currently the md5 hash of the template content. This however makes it difficult to track log events for a template over time for all changes to the content.
Metrics have been recently added to Consul Template #1378 and is also using the template hash as its ID.
In addition to having a consistent identifier for a template, it would be ideal for the identifier to be easily mapped to a template. It is not immediately clear in the above example which hash corresponds to which template.
Consul Template version
consul-template v0.25.0 (99efa64)
Configuration
Config:
test.hcl
Consul KVs
Command
Debug output
Steps to reproduce
"hello, {{ key \"hello\" }}"
SIGHUP
signal to reload config/templateExpected behavior
Consistent identifier for a template even upon changes to its content.
This is not a bug, and the template IDs changing are expected on reload since the identifier of templates are currently the md5 hash of the template content. This however makes it difficult to track log events for a template over time for all changes to the content.
Metrics have been recently added to Consul Template #1378 and is also using the template hash as its ID.
In addition to having a consistent identifier for a template, it would be ideal for the identifier to be easily mapped to a template. It is not immediately clear in the above example which hash corresponds to which template.
References
The text was updated successfully, but these errors were encountered: