Skip to content

fix: propagate event when resource is marked for deletion#3397

Closed
csviri wants to merge 1 commit into
mainfrom
marked-for-deletion-event
Closed

fix: propagate event when resource is marked for deletion#3397
csviri wants to merge 1 commit into
mainfrom
marked-for-deletion-event

Conversation

@csviri
Copy link
Copy Markdown
Collaborator

@csviri csviri commented Jun 6, 2026

No description provided.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 6, 2026
Copy link
Copy Markdown
Collaborator

@xstefank xstefank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@csviri also port the test please

@csviri
Copy link
Copy Markdown
Collaborator Author

csviri commented Jun 8, 2026

@csviri also port the test please

yes, will do, thx

@csviri
Copy link
Copy Markdown
Collaborator Author

csviri commented Jun 8, 2026

replaced by: #3399

@csviri csviri closed this Jun 8, 2026
@metacosm metacosm deleted the marked-for-deletion-event branch June 8, 2026 08:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants