Added ItemBlockAction plugin and example test data #74
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 PR adds an ItemBlockAction plugin as part of the documentation effort for the new Velero 1.15 plugin type.
The test data in examples/itemblock-pods.yaml will create two deployments whose pods will be included in a single ItemBlock -- this can be seen in the backup logs by looking at the order of the pre and post hooks which are defined in the test data. Without a shared ItemBlock, you would see logging for pre and post hook for pod1, followed by logging for pre and post hook of pod2. With the ItemBlock defined as specified in the example plugin, you will see both pre hooks run, followed by backing up the pods (and associated volumes, etc.), followed by both post hooks.