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
{{ message }}
This repository has been archived by the owner on Jun 18, 2022. It is now read-only.
So, I'm having trouble trying to get zen discovery working with the confd configuration provided by the elasticsearch-conf package. There seems to be two problems:
The {{range ls "/self/service/metadata/elasticsearch/yml"}} command produces a value called "self" which causes the {{getv (printf "/self/service/metadata/elasticsearch/yml/%s" .)}} call to fail since that key does not exist in the rancher meta data.
The other issue is this call, {{ $containerName := getv (printf "/self/service/containers/%s" .)}} fails. This is odd considering that if I make a curl request to curl http://rancher-metadata/latest/self/service/containers I do in fact see the container that the template is trying to use.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So, I'm having trouble trying to get zen discovery working with the confd configuration provided by the elasticsearch-conf package. There seems to be two problems:
{{range ls "/self/service/metadata/elasticsearch/yml"}}
command produces a value called "self" which causes the{{getv (printf "/self/service/metadata/elasticsearch/yml/%s" .)}}
call to fail since that key does not exist in the rancher meta data.{{ $containerName := getv (printf "/self/service/containers/%s" .)}}
fails. This is odd considering that if I make a curl request tocurl http://rancher-metadata/latest/self/service/containers
I do in fact see the container that the template is trying to use.The text was updated successfully, but these errors were encountered: