You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the ResourceRecordSet resource, the name of the resource is the name of the record. This is all well and good, unless you want to be able to create more than one record of the same name in different zones. Say I have an ArgoCD app and a r53 record controlled by that app. I want to put this record in both Zone A and Zone B. I am unable to create two instances of ResourceRecordSet because the names of the resources are the same, and you can only provide one Zone ID to place the record in the resource object.
How could Crossplane help solve your problem?
It would be great if this can be supported by implementing the following to the resource manifest:
Add a new optional parameter to the ResourceRecordSet resource called zoneIds or something similar that accepts a list of zone IDs to create the record. Add constraints such that only one of zoneId, zoneIds, zoneIdRef, or zoneIdSelector may be defined.
The text was updated successfully, but these errors were encountered:
What problem are you facing?
In the
ResourceRecordSet
resource, the name of the resource is the name of the record. This is all well and good, unless you want to be able to create more than one record of the same name in different zones. Say I have an ArgoCD app and a r53 record controlled by that app. I want to put this record in both Zone A and Zone B. I am unable to create two instances ofResourceRecordSet
because the names of the resources are the same, and you can only provide one Zone ID to place the record in the resource object.How could Crossplane help solve your problem?
It would be great if this can be supported by implementing the following to the resource manifest:
Add a new optional parameter to the
ResourceRecordSet
resource calledzoneIds
or something similar that accepts a list of zone IDs to create the record. Add constraints such that only one ofzoneId
,zoneIds
,zoneIdRef
, orzoneIdSelector
may be defined.The text was updated successfully, but these errors were encountered: