ghe-host-check -F configfile #481
Closed
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
aferreira
force-pushed
the
host-check-config
branch
from
5d9eca0
to
2618060
Compare
This is meant to check against the hostname of a config file
that was not put into place yet. Works like
GHE_BACKUP_CONFIG=configfile ghe-host-check
but with a documented -F option.
One use case is validating a newly generated backup.config file
before putting it into production (for example, via Puppet).
aferreira
force-pushed
the
host-check-config
branch
from
2618060
to
01a85b1
Compare
|
Sorry for the delay on this one, I'm going to close this out since the desired usage of the tool can already be achieved today with the outlined command: |
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.
This is meant to check against the hostname of a config file
that was not put into place yet. Works like
but with a documented -F option.
One use case is validating a newly generated
backup.configfilebefore putting it into production (for example, via Puppet).