Add test mechanism for plugin operation failure (WIP) (main) #7043
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
This change adds a check to the plugin framework which checks plugin property maps for the "munge_operations" keyword. Currently, the keyword must contain a value that is a comma-delimited list of key-value pairs separated by colons. This is meant to provide a means for testing to configure a plugin (at this time, only resource plugins are being tested) such that certain operations return specific error codes. This adds some tests which ensure that the system is behaving properly when certain resource plugin operations fail. Specifically, when a data object is created and some resource plugin operation fails, the data object should be marked stale to ensure that the state of the data is properly reflected in the catalog.
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.
Used this to confirm that the Glacier concerns in #6997 have been addressed, rather than actually setting up a Glacier resource.
This is a work in progress and may never be merged.