This PR takes provider conformance a step further by smoke testing that all managed resources defined by a provider can become ready, and populate their crossplane.io/external-name annotation. We rely on the person running the conformance test to manually create one of each kind of managed resource before running the test. I can't think of a great way to avoid this given that the conformance test logic can't know the schema, credentials, etc required to spin up and down managed resources.
Signed-off-by: Nic Cope negz@rk0n.org
Description of your changes
Advances https://github.com/crossplane/conformance/issues/10
This PR takes provider conformance a step further by smoke testing that all managed resources defined by a provider can become ready, and populate their
crossplane.io/external-nameannotation. We rely on the person running the conformance test to manually create one of each kind of managed resource before running the test. I can't think of a great way to avoid this given that the conformance test logic can't know the schema, credentials, etc required to spin up and down managed resources.I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
I've created a simple resource (a GCS bucket) and confirmed it passes the test.