Fix default config file location for some services #4596
Merged
Conversation
This file contains hidden or 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
correctly use default config file from /etc/st2/st2.conf if one is not explicitly provided using --config-file command line argument.
Kami
added a commit
that referenced
this pull request
Mar 14, 2019
Kami
added a commit
that referenced
this pull request
Mar 14, 2019
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.
Some services (
st2actionrunner,st2scheduler,st2workflowengine) didn't specify a default path to the config file (/etc/st2/st2.conf) so they would fail to start (e.g. in a dev environment) if--config-fileargument was not explicitly provided.Other services already correctly handle that.
This pull request fixes that.
Related to #4111.