Examples for HTTP based task-group service healthchecks are
covered by the `countdash` demo, but gRPC checks currently
have no runnable examples.
This PR adds a trivial gRPC enabled application that provides
a Service implementing the standard gRPC healthcheck interface.
The provision shell script tries to install libssl1.1 package as dependency of ca-certificates package.
The installing of libssl requires to restart some services, and it asks for confirmation of this.
But there are no interactive session at this stage, so Vagrant provisioning just hungs.
This commit add a `libraries/restart-without-asking boolean true` setting before installing libssl,
so it doesn't ask confirmation anymore and the provisioning works again.
Give demo agents unique names to improve `nomad node status` output.
Since the agents default to the hostname, they all had the same name
whether using the root or demo Vagrantfiles.
* 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
* 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
