-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
acl bootstrap -json #10880
Comments
Hey @tomlankhorst, this definitely seems like a good idea, especially since it is in Consul as well. Unfortunately, it isn't super high priority for the team, so I worry that the issue might sit here un-done for a while (even though its a valid request). Would you be open to opening a PR for this? It seems like an ideal community PR since there is pretty clear success criteria, no coupling with the rest of the codebase, and the Consul code could be used for inspiration. |
This has now been resolved by #11411 and will be available within the Nomad 1.2.0 release. |
Thanks a lot! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Proposal
Add
-json
formatting toacl bootstrap
Analogous to
consul acl bootstrap -format=json
.Use-cases
Easy automatic deployment of ACL in new Nomad clusters
BOOTSTRAP_TOKEN=$(nomad acl bootstrap -json | jq -r '.SecretID')
Attempted Solutions
Parse the human-readable output, but this is not stable or elegant.
BOOTSTRAP_TOKEN=$(nomad acl bootstrap | awk '/Secret/ {print $4}')
The text was updated successfully, but these errors were encountered: