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 Nov 16, 2022. It is now read-only.
we now use "injected" vault auth tokens for workflows, and if this is done we need to set the auth type for Vault correctly. Earlier we where checking for a environment variable in the workflow docker container, but as this is now gone we need to detect for something else, f.e. the label that we set to trigger token injection. We also need to make sure that the injected token is passed in the config. The related line of code:
olafmol
changed the title
when using Vault the auth type is not set correctly for confd
when using Vault as k/v the workflow process fails
Nov 21, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
we now use "injected" vault auth tokens for workflows, and if this is done we need to set the auth type for Vault correctly. Earlier we where checking for a environment variable in the workflow docker container, but as this is now gone we need to detect for something else, f.e. the label that we set to trigger token injection. We also need to make sure that the injected token is passed in the config. The related line of code:
vamp-workflow-agent/files/etc/service/confd/run
Line 17 in c311d73
The text was updated successfully, but these errors were encountered: