Externalized the plugins package 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:
Adhere to the phase 1.5 plugin criteria that would allow the Operator SDK to eventually have a dependency on this repository and import the plugin for use within the Operator SDK binary.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
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