Christopher Haar

/fresh

ref: https://github.com/crossplane/crossplane/issues/4047

with the v0.10.0 release you can ignore fields and add an override patch: https://github.com/crossplane-contrib/x-generation/blob/main/package/EKS-Cluster/generate.yaml#L18-L26

@stevendborrelli after we merge https://github.com/crossplane-contrib/x-generation/pull/29 we have the option to use `EnvironmentConfig` like this - does this makes sense for your ? ``` group: eks.aws.example.cloud name: Cluster version: v1beta1 provider:...

is released with v0.10.0 checkout: https://github.com/crossplane-contrib/x-generation/blob/main/package/EKS-Cluster/generate.yaml#L27-L28

i know ;) thats why its a draft - but with this branch we can use provider-argocd in functions

https://github.com/upbound/platform-ref-aws/blob/main/package/cluster/eks/composition.yaml#L227 set readinessCheck to none

the same we have in provider-pagerduty ``` rule: - escalationDelayInMinutes: 10 target: - id: ${pagerduty_user.example.id} type: user_reference - id: ${pagerduty_user.example2.id} type: user_reference ```

in official-provider upbound/provider-aws we can see the same https://marketplace.upbound.io/providers/upbound/provider-aws-directconnect/v0.36.0/resources/directconnect.aws.upbound.io/GatewayAssociation/v1beta1#doc:spec-forProvider-associatedGatewayId associatedGatewayId is possible to match multiple resource types today its only possible to select / reference one resource type https://marketplace.upbound.io/providers/upbound/provider-aws-directconnect/v0.36.0/resources/directconnect.aws.upbound.io/GatewayAssociation/v1beta1#doc:spec-forProvider-associatedGatewayIdRef

Any Suggestion for Implementation ?