{{ range secrets "main/env/users" }}
{{ with secret (printf "main/env/users/%s" .) }}
echo "For {{ .Data.name }} now value1 this is {{ .Data.value1 }}"
{{ end }}{{ end }}
{{ with secret "main/env/users/user1" }}
echo "---direct ----- for {{ .Data.name }} now value this is {{ .Data.value }}"
{{ end }}
{{ with secret "main/env/users/user2" }}
echo "---direct ----- for {{ .Data.name }} now value this is {{ .Data.value }}"
{{ end }}
in Vault storage (kv1 Secret engine) created 2 secrets: main/env/users/user1 and main/env/users/user1
with same keys and different values : name={user1,users2} and value={value1, value2} accordingly.
Expected behavior
1 ) Consul-template should read data from secretes.
2) After changed value in Vaul -> Consul-template should update the value in template.
Actual behavior
1) Consul-template has read data from secrets and rendered correctly:
echo "For user1 now value1 this is value1 "
echo "For user2 now value1 this is value2 "
2) After changing the value in Vault Consul-template uses/renders old value
Steps to reproduce
Create secret in Vault and use it in Consul-template
Consul Template version
consul-template v0.29.6 (e4f5d58)
Configuration
in Vault storage (kv1 Secret engine) created 2 secrets: main/env/users/user1 and main/env/users/user1 with same keys and different values : name={user1,users2} and value={value1, value2} accordingly.
Expected behavior
1 ) Consul-template should read data from secretes. 2) After changed value in Vaul -> Consul-template should update the value in template.
Actual behavior
1) Consul-template has read data from secrets and rendered correctly: echo "For user1 now value1 this is value1 " echo "For user2 now value1 this is value2 " 2) After changing the value in Vault Consul-template uses/renders old value
Steps to reproduce