This repository has been archived by the owner on Aug 9, 2021. It is now read-only.
Move policies to files per category #462
Merged
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
![accesslint[bot]](https://avatars.githubusercontent.com/in/1502?s=60&v=4){kind=small}
btry
force-pushed
the
feature/policies_definition_install
branch
2 times, most recently
from
97fa915
to
e1294be
Compare
ajsb85
previously approved these changes
Apr 29, 2018
Signed-off-by: Thierry Bugier <[email protected]>
btry
force-pushed
the
feature/policies_definition_install
branch
from
e1294be
to
a9fc433
Compare
DIOHz0r
approved these changes
Apr 30, 2018
ajsb85
approved these changes
Apr 30, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Code a bit more complex because all policies files use a variable set out of them (in installer), but this makes the code way more modular. This also helps to move policies from a category to an other when needed.
Beware about #430 #444 and #457. Depending on the order of merge, some of these PR -this one included) will need an update.
Closes #449