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 Jan 25, 2023. It is now read-only.
We can.
We try to leverage run-consul, run-nomad, and even run-vault out of the box, but are finding that we're having to skip the config anyway because we need new vars passed through from terraform to the script to pass into run-nomad to generate the config file properly.
For example, the vault stanza in nomad takes in custom data like custom_from_role and token. These vars are not supported by run-nomad on the command line as-is.
In the end, we built our own custom generate-nomad-config script supporting our additional parameters.
I don't think it would be maintainable for run-nomad to support every parameter. It should support the ones that affect, say, 80-90% of users, and for the rest, using a custom config file and then calling run-nomad is the recommended way to go. You can package the custom config file with your AMI. If there is some data that must be passed in at run-time, you can pass that in via User Data.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
run-nomad does not currently support the vault stanza for vault integration with server or client
This would add
vault {
enabled
address
create_from_role
token
}
at a minimum.
The text was updated successfully, but these errors were encountered: