(feat): Externalize the plugins package
#3
Merged
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.
Description of the change:
pluginspackage so that the plugin can be used as a phase 1.5 (external library) plugin by the Operator-SDK. This only externalizes the plugins package and does a bit of clean up. The testdata is still currently generated by using the baked in Operator-SDK binary but this test data generation logic is likely best updated in a follow up PR. For now I have a WIP PR up in the Operator-SDK repo showing the importing and use of this package.This is an incremental step towards getting this to be a phase 2 plugin while allowing the Operator SDK to take incremental steps toward using an external ansible operator plugin.
Motivation for the change:
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs