68947cfca6
When a delete of a resource is requested a `deletionTimestamp` is set on the resource by the requester, this also results in a generation change of the resource. If the resource is under reconciliation while this timestamp is set, and had not produced an artifact earlier on, this becomes a problem as the artifact metadata is used to determine what should be garbage collected on a deletion, resulting in stray files for resources that are no longer present. To resolve this for now, we always create a new artifact object for the resource when `all==true` on the GC method call, and no longer rely on the presence of the artifact object on the resource itself. |
||
|---|---|---|
| .. | ||
| testdata | ||
| gitrepository_controller.go | ||
| gitrepository_controller_test.go | ||
| helmchart_controller.go | ||
| helmchart_controller_test.go | ||
| helmrepository_controller.go | ||
| helmrepository_controller_test.go | ||
| predicate.go | ||
| storage.go | ||
| storage_test.go | ||
| suite_test.go | ||
| util.go | ||