Open ytsarev opened 2 years ago
If we look at the following examples of https://github.com/crossplane-contrib/provider-jet-datadog/blob/main/examples/monitor/monitor.yaml#L4-L8 and https://github.com/crossplane-contrib/provider-jet-datadog/blob/main/examples/monitor/servicelevelobjective-metric.yaml#L4-L7 we are duplicating name between metadata.name and spec.forProvider.name.
metadata.name
spec.forProvider.name
It also can be a desired scenario because spec.forProvider.name can have a longer descriptive name and metada.name is limited to https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names.
metada.name
We need more feedback on the provider consumers before acting on this proposal.
Rely only on metadata.name and populate spec.forProvider.name automatically in case it is required
What problem are you facing?
If we look at the following examples of https://github.com/crossplane-contrib/provider-jet-datadog/blob/main/examples/monitor/monitor.yaml#L4-L8 and https://github.com/crossplane-contrib/provider-jet-datadog/blob/main/examples/monitor/servicelevelobjective-metric.yaml#L4-L7 we are duplicating name between
metadata.nameandspec.forProvider.name.It also can be a desired scenario because
spec.forProvider.namecan have a longer descriptive name andmetada.nameis limited to https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names.We need more feedback on the provider consumers before acting on this proposal.
How could Datadog Provider help solve your problem?
Rely only on
metadata.nameand populatespec.forProvider.nameautomatically in case it is required