Ensure postgresql service is started after configuration even with no configuration change #24
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
added 4 commits
December 6, 2024 09:58
This helps in cased engine was stopped, and there is no config change so no handler is executed to reload the service
… of postgres As postgres_users_no_log was just documented accross, the role, support for it is still included to not cause any breacking change
davidassigbi
deleted the
23-ensure-postgresql-service-is-started-after-configuration-even-with-no-configuration-change
branch
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.
Description
Ensure postgresql service is started after configuration even with no configuration change
closes #22
closes #23
Motivation and Context
How Has This Been Tested?
Tests performed with Molecule both locally and using Github Actions
Types of Changes
Checklist: