SAP / SAP/component-operator-runtime
[BUG] Unintuitive behavior of delete-policy: orphan-on-apply
@cbarbian-sap is already working on this.
Since Jul 18, 2026.
- Dominant language
- Go
- Stars
- 6
- Forks
- 4
- Avg merge
- 17h 17m
- Merged PRs (30d)
- 11
Description
Describe the bug
Objects having been orphaned due to an effective deletion policy OrphanOnApply are not deleted when the owning component itself is deleted.
This is probably logical in the intrinsic logic of the framework (because, being already orphaned, they are no longer dependents of the component, so they are not considered during the component deletion).
Tested with Version
v0.3.156
Expected behavior
But most users probably expect something different to happen: that those objects then finally are removed along with the component.
Additional context
We should improve this. Either by semantically changing the semantics of OrphanOnApply , or by introducing a another deletion policy, such as OrphanOnApplyAndDeleteDuringDeletion. Note that in any case we would have to keep the inventory record of every object which was orphaned during an apply. Which might blow up the inventory significantly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.