cloud sql user manual-intervention "Depends on SQL instance to be successfully deleted"

[crossplane-contrib]

cloud sql user manual-intervention "Depends on SQL instance to be successfully deleted"

[gberche-orange]

@turkenf I see commit 597337c replaced the upjet.upbound.io/manual-intervention with uptest.upbound.io/pre-delete-hook: testhooks/delete-user.sh, see 597337c#diff-10002ef5d36e299d3a4c9b570c82006c79f5c3176761eff6b84a5c595b5014a0

while upjet documentation still mentions

https://github.com/upbound/upjet/blob/main/docs/add-new-resource-short.md#testing

There are cases where the resource requires user to take an action that is not possible with a Crossplane provider or automated testing tool. In such cases, we should leave the actions to be taken as annotation on the resource like the following:
[...]
upjet.upbound.io/manual-intervention: "User needs to upload [...]

Should users now look instead at the uptest.upbound.io/pre-delete-hook annotation?

Any chance to share a bit of analysis to the root cause of this issue ?

Is there any declarative workaround to document for crossplane users ?
@bobh66 had planned for sharing its kyverno mutation policy early jan, but I haven't yet seen it.

[turkenf]

Should users now look instead at the uptest.upbound.io/pre-delete-hook annotation?

Yes with hook support in uptest, we can now automate testing resources which require ordered deletion. We actually use these annotations to make our examples uptestable in our tooling system.

[github-actions]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions]

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!