OWLS-70527 : version.txt support in situational config #579
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
tbarnes-us
suggested changes
Dec 6, 2018
tbarnes-us
reviewed
Dec 6, 2018
tbarnes-us
reviewed
Dec 6, 2018
vkraemer
changed the title
tbarnes-us
reviewed
Dec 6, 2018
tbarnes-us
approved these changes
Dec 6, 2018
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.
Added code to generate an error if the user does not include a version.txt file in their situational config directory.
The version.txt must have the content "2.0" to be accepted in Operator 2.0. Future versions could use this versioning to guide parsing or the custom config files. Could is the operative word...