-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cli: update nomad job init full examples #24232
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
schmichael - Thanks for including me! Some style guide suggestions:
- changed "please see" to "refer to". We are not supposed to use "see"
- changed future tense to present tense
- changed passive voice to active voice where it made sense
I'll add a new page to the team-nomad wiki with the aforementioned style guidelines plus how to engage the docs team (which is currently in Confluence but the Eng team doesn't look there).
command/asset/example.nomad.hcl
Outdated
# | ||
# For more information and examples on the "template" block, please see | ||
# the online documentation at: | ||
# For more information and examples on the "template" block, please see: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# For more information and examples on the "template" block, please see: | |
# For more information and examples on the "template" block, refer to: |
command/asset/example.nomad.hcl
Outdated
# and revocation of the Vault token. | ||
# The "vault" block instructs the Nomad client to acquire a token from a | ||
# HashiCorp Vault server. Nomad must be configured to communicate with | ||
# Vault. By default, Nomad will inject the token into the task via an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Vault. By default, Nomad will inject the token into the task via an | |
# Vault. By default, Nomad injects the token into the task via an |
command/asset/example.nomad.hcl
Outdated
# The "vault" block instructs the Nomad client to acquire a token from a | ||
# HashiCorp Vault server. Nomad must be configured to communicate with | ||
# Vault. By default, Nomad will inject the token into the task via an | ||
# environment variable and make the token available to the "template" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# environment variable and make the token available to the "template" | |
# environment variable and makes the token available to the "template" |
command/asset/example.nomad.hcl
Outdated
# | ||
# For more information and examples on the "vault" block, please see | ||
# the online documentation at: | ||
# For more information and examples on the "vault" block, please see: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# For more information and examples on the "vault" block, please see: | |
# For more information and examples on the "vault" block, refer to: |
Co-authored-by: Aimee Ukasick <[email protected]>
The full example jobspecs emitted by
nomad job init
andnomad job init -connect
have not seen any improvement in over a year. I intended to just peek in, add a newui{}
block block, and be done. However, something about skimming over the phrasethe online documentation
a dozen times made me stop and do some spring cleaning.The diff is an absolute nightmare even though I think my changes are fairly minor. Some highlights:
ui
block because I think it should be a widely used feature!affinity{}
.the online documentation
. It is 2024, not 1999. I think our users know what a URL implies.affinity{}
and all of its field comments, so I just removed the field comments. I think users are much better off visiting the online documentation for those details. The examples should demonstrate Nomad's featureset, not be a comprehensive guide to those features.Pinging @philrenaud because I've been pestering Phil with
ui{}
things already, and @aimeeu because despite this being a part of thenomad
binary, I think it's documentation, and I want to make sure my changes fit with the style of similar examples our docs are full of. Let me know if you want to hand it off.