You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have examples manifests in each provider but not all of them can work in Uptest.
How could Official Providers help solve your problem?
There are roughly the following classes of resources:
Examples of inherited resources from Jet providers.
These were assumed to be working since we had merged them with manual testing but that's not the case for all of them.
Examples we merged after a report of manual testing.
We manually tested and reported the results in the PR body before Uptest was ready to be used for all scenarios.
Examples that require manual intervention, like file upload, but not marked as such.
Ideally, we should make all manifests be able to go through Uptest without errors so that we can run the pipeline whenever we need to, like TF provide upgrade, and not get false negatives.
In order to reach that, we should do a pass over them to fix bugs and mark the ones that require manual intervention with uptest.upbound.io/manual-intervention annotation to tell users what they need to do and to instruct Uptest to skip that specific resource during testing. Later, we can improve Uptest to take those actions and remove the annotations over time. But first, we need to get to a place where all examples can be run with Uptest without error.
This is an epic issue, related current issues are:
luebken
changed the title
Have all manifests in example YAML be able to go through Uptest
[Epic] Have all manifests in example YAML be able to go through Uptest
Aug 15, 2022
What problem are you facing?
We have examples manifests in each provider but not all of them can work in Uptest.
How could Official Providers help solve your problem?
There are roughly the following classes of resources:
Ideally, we should make all manifests be able to go through Uptest without errors so that we can run the pipeline whenever we need to, like TF provide upgrade, and not get false negatives.
In order to reach that, we should do a pass over them to fix bugs and mark the ones that require manual intervention with
uptest.upbound.io/manual-intervention
annotation to tell users what they need to do and to instruct Uptest to skip that specific resource during testing. Later, we can improve Uptest to take those actions and remove the annotations over time. But first, we need to get to a place where all examples can be run with Uptest without error.This is an epic issue, related current issues are:
More issues will be needed for the rest of the resources until
/test-examples="provider-{aws,gcp,azure}/examples"
works.The text was updated successfully, but these errors were encountered: