Add support for deleting parent paths of matches #1
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
Allows you to delete the parent paths of matched items instead of the items themselves. Particularly useful for cleaning up Docker images, I imagine.
praqma-thi
force-pushed
the
delete-parent
branch
from
739b9e5 to
417df98
Compare
praqma-thi
force-pushed
the
delete-parent
branch
from
417df98 to
0886124
Compare
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.
Adds support for templates to specify a
deleteParentproperty, which would allow users to specify they want the parent paths of FileSpec matches to be deleted, rather than the matches themselves.This will allow users to delete artifact directories if they contain an artifact matching their conditions.
This could also be used to delete Docker images based on conditions of their manifest.json, for example.
As for the implementation, if a policy has
deleteParentset to true, rather than expanding the template directly into a resulting FileSpec, we generate the FileSpec, search for matches, and generate a FileSpec that matches the parent paths of the result.