chore(controllers): Test CR deletion, Update finalizer behaviour of Dashboard, Datasource, and Folder #2098
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.
The initial goal was to just delete created CRs and trigger the finalizer.
Unfortunately
GrafanaDashboard
,GrafanaDatasource
, andGrafanaFolder
all returned successful when attempting to finalize against thedummy
Grafana instance used to provoke Synchronization failures.I removed the early exit in favour of attempting and potentially failing to delete the resource.
All finalizers will now return a success if the resource was deleted or didn't exist, and an error otherwise.
This should lead to a few more requests when finalizing resources, but more correct deletion outcomes in edge cases.
The downside of this is the need to expect an error when the
dummy
instance, which never responds, is being deleted from.