Christoph Schwägerl

To me this proposal looks like it goes in to the direction of what I would intuitively expected from traits. As of the current porposal, is this not just the...

> Yes, I also interpreted the JSON Merge patch behavior that arrays get replaced and not merged there as well. This would correspond to the simpler merge algorithm I stated...

@magicmatatjahu yeah I see where you are coming from. Maybe that could be addressed by configurable *plain* vs *effective* flavor. Using effective means you validate the end result of the...

Another sub-issue: https://github.tools.sap/kyma/test-infra/issues/735

Also related to: https://github.com/kyma-project/community/issues/921

Feedback 2025-03-12: - we can enforce the need for default Module CR in the publishing pipeline - consumers can expect the data to be present, but should be robust to...

Thanks for explaining. From lifecycle-manager perspective, the most important use case for the module CR is the safe deletion, see https://github.com/kyma-project/community/issues/972. If there is no module CR, lifecycle-manager will immediately...

Feedback 2025-03-12: - `CustomResourcePolicy: CreateAndDelete` is a convenience feature for the customer - eventually, the customer needs to take care of cleaning up every module-related configuration before the deletion happens...

Feedback 2025-03-12: - simplify the KLM check by looking up all resources from the Module CRD - if none exist => go ahead with deletion - if at least one...

Addendum from 2025-04-23: For CRP `CreateAndDelete`, lifecycle-manager will continue to mark the default Module CR for deletion (not any other customer-created Module CR). Further action item: explore an evolution of...