Value Statement

The current cloudevent sdk lacks support for garbage collection (GC) mechanisms similar to Kubernetes. When transporting manifestworks through cloudevents drivers, there's no automatic garbage collection process akin to Kubernetes.

For instance, in cases of cascading deletion, where a manifestwork is associated with an owner reference, the manifestwork should ideally be deleted in the background when the owner is deleted. However, this functionality is absent in the current implementation.

We need to enhance the cloudevents sdk to include garbage collection capabilities, ensuring efficient resource management in cloudevents contexts.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.