Problem
KymaModule MR has no support for external name now.
We need to set it during Create and use it for matching during observe.
First evaluate if KymaModule can have external name support since it maps the MR to one cr in the Kyma Cluster. It might not need external-name support for the export/import functionality.
NOTE: follow the external-name ADR here https://github.com/SAP/crossplane-provider-btp/blob/main/docs/development/external-name-handling.md
Context
During Create external-name is set to forProvider.name. Kyma CR contains a list of modules in this cluster, one KymaModule is only mapped into this list. There is no unique key besides the module name. Every module can only exist once with one channel specified. Choosing a forProvider.name is a parameter and unique key.
Acceptance Criteria
Problem
KymaModuleMR has no support for external name now.We need to set it during Create and use it for matching during observe.
First evaluate if KymaModule can have external name support since it maps the MR to one cr in the Kyma Cluster. It might not need external-name support for the export/import functionality.
NOTE: follow the external-name ADR here https://github.com/SAP/crossplane-provider-btp/blob/main/docs/development/external-name-handling.md
Context
During Create external-name is set to
forProvider.name. Kyma CR contains a list of modules in this cluster, oneKymaModuleis only mapped into this list. There is no unique key besides the module name. Every module can only exist once with one channel specified. Choosing aforProvider.nameis a parameter and unique key.Acceptance Criteria