-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cross-resource references to handle multiple types #350
Comments
When creating an Opsgenie Escalation the recipient type can be either Below is an example on how it could look like with multi cross-resource reference. ...
spec:
forProvider:
name: Escalation Name
rules:
- recipient:
- type: user
userIdRef:
name: user-name
- type: team
teamIdRef:
name: team-name
- type: schedule
scheduleIdRef:
name: schedule-name Terraform example.
https://registry.terraform.io/providers/opsgenie/opsgenie/latest/docs/resources/escalation |
the same we have in provider-pagerduty
|
in official-provider upbound/provider-aws we can see the same 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 |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
What problem are you facing?
There are fields in some resources that could be fulfilled by different types, i.e. ARN of
Instance
orNetworkInterface
orLoadBalancer
could be given. However, cross-resource resolver always works with a singe hard-coded type so you have to use composition to patch those fields.How could Crossplane help solve your problem?
We could either solve this via generic patching or implement #341 and have per-type resolver logic in the code so that we don't have to ask for fieldpaths, transforms etc.
The text was updated successfully, but these errors were encountered: