The sample request incorrectly used `https://nomad.rocks/v1/job/my-job/deployments` which listed all deployments for the specified job. The sample request has therefore been updated to use the correct endpoint which returns only the jobs most recent deployment.
In a content reorganization, the allocations endpoint documentation was removed. This just brings it back in and updates the output to match v0.6.0 output
This PR fixes an incorrect placement of the update stanza in the task
and also links from the env stanza into an example of using the template
block to generate dynamic environment variables.
* hclfmt the world
* 2 space indent
* make every example well formed with stanzas and comments
* jsonfmt too
* mdfmt manually
* _ instead of *
* no [links][], only [links][links]
* ordered lists instead of bullets when possible
* lots of wording fixes
* de-contractionization
* add 127.0.0.1 to SANs
* -1 on intentional errors
* -1 on first person
This will create a concrete mention of job anti-affminity in the Nomad documentation. The only place we discuss it currently is in a similar sentence on the website itself. I borrowed liberally from that sentence in crafting this line.
This PR enhances the distinct_property constraint such that a limit can
be specified in the RTarget/value parameter. This allows constraints
such as:
```
constraint {
distinct_property = "${meta.rack}"
value = "2"
}
```
This restricts any given rack from running more than 2 allocations from
the task group.
Fixes https://github.com/hashicorp/nomad/issues/1146
We only mention job anti-affinity on the main webpage. This sentence is borrowed from there with minor tweaks to at least introduce it in the docs corpus
* Update operating a job, upgrade guide
This PR updates the guide for updating a job to reflect the changes in
Nomad 0.6
* Feedback changes
* Feedback
* Feedback
* Add new commands for 0.6
* update version in documnetation for 0.6
* more information in example.nomad
* 0.6 additional information for viewing status of a job
* 0.6 status for alloc-status
* changes with 0.6 in modifying a job
* status is healthy when consul is running
* make new date consistent in
* add Latest Deployment and Deployed sections to output
* small changes in status values so that things the user should see as thesame, are the same in the example (e.g. Node ID should be the same in all places we list it in the example)
* further information in job status added in 0.6
* update output when changing redis version
* make new date consistent in
* add Latest Deployment and Deployed sections to output
* small changes in status values so that things the user should see as thesame, are the same in the example (e.g. Node ID should be the same in all places we list it in the example)
* Add new commands for 0.6
* update version in documnetation for 0.6
* more information in example.nomad
* 0.6 additional information for viewing status of a job
* 0.6 status for alloc-status
* changes with 0.6 in modifying a job
* status is healthy when consul is running
* further information in job status added in 0.6
* evaluation status for deployment in 0.6
* updating client demo config to match website
* update output of status for cluster
* update output when changing redis version
* update terminal output of adding more redis instances.
* small update so id numbers are consistent in example
* update ouput for , also stitch up ids from previous lines to match
* add to output when starting server and clients
* add to output
* remove text showing large parts of example.nomad file
* Small fixes to stopping and updating a job
Michael Schurter