Update VMClarity init so stack upgrades apply correctly #253
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.
Description
This change tweaks the init configs for VMClarity server so that cfn-hup and cfn-init hooks restart the services correctly when the cloud formation stack updates the VMClarity server configuration.
Without this change the cfn-hup and cfn-init notice the change and update the systemd unit files, but the services don't get restarted so they continue to run the old version.
This change also lowers the cfn-hup polling time from 15 minutes to 5 minutes, so that the VMClarityServer notices that the cloudformation has been updated sooner.
Type of Change
[X] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)
Checklist