Use contain
to declare classes to allow relationships
#3
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 allows to create relationships between external classes and this class.
Given the following snippet to create and configure a new subpolicy:
It won't be executed in the right order despite the
notify
.crypto_policies::config
is executed before and fails, as the subpolicy file does not yet exist:With contain, classes are contained and relationships work:
An alternative would be to use
notify => Class['crypto_policies::config']
, but I consider the config class as private.Swapping class and file declaration order would make it dependent on parse-order.