feat: display node id on start up for servers #17084
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Bram Vogelaar <[email protected]>
tgross
approved these changes
May 18, 2023
There was a problem hiding this comment.
LGTM! Thanks @attachmentgenie!
$ nomad agent -config=/etc/nomad.d/server.hcl -log-level=info
==> WARNING: mTLS is not configured - Nomad is not secure without mTLS!
==> WARNING: Bootstrap mode enabled! Potentially unsafe operation.
==> Loaded configuration from /etc/nomad.d/server.hcl
==> Starting Nomad agent...
==> Nomad agent configuration:
Advertise Addrs: HTTP: 192.168.1.46:4646; RPC: 192.168.1.46:4647; Serf: 192.168.1.46:4648
Bind Addrs: HTTP: [0.0.0.0:4646]; RPC: 0.0.0.0:4647; Serf: 0.0.0.0:4648
Client: false
Log Level: debug
Node Id: 22ec19f8-b2bb-385e-5515-063c80699db4
Region: global (DC: dc1)
Server: true
Version: 1.5.4-dev
==> Nomad agent started! Log data will stream in below:
...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The outage recovery document mentions that the node id can be found at start up. However this isnt't true at current time, this PR fixes that.