Backport of Resolves issue-16844 - systemd notify by default into release/1.14.x #17562
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.
Backport
This PR is auto-generated from #16845 to be assessed for backporting due to the inclusion of the label backport/1.14.
The below text is copied from the body of the original PR.
consul.service
systemd service unit to useType=notify
to resolve issue systemd unit does not use systemd notify, documentation doesn't provide example of using systemd notify #16844Description
To resolve issue #16844 and switch packaged systemd unit to use systemd's notify mechanism by default.
Testing & Reproduction steps
See #16844 where the steps to reproduce the current and updated behavior are documented
Links
#2121
31a310f
https://developer.hashicorp.com/consul/docs/agent#understanding-the-agent-startup-output
https://developer.hashicorp.com/consul/tutorials/production-deploy/deployment-guide#configure-the-consul-process
PR Checklist
Overview of commits