Fix usage of static 'elasticsearch' instead of $elasticsearch::service_name
#1178
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
smortex
approved these changes
Dec 16, 2022
smortex
changed the title
'elasticsearch' instead of $elasticsearch::service_name
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.
Pull Request (PR) description
Replace static service name 'elasticsearch' by $elasticsearch::service_name
This Pull Request (PR) fixes the following issues
When Elasticsearch is installed with a custom service_name, puppet will fail because the custom name is not used for the before relationship metaparameter.
results in:
Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Could not find resource 'Service[elasticsearch]' in parameter 'before'