Forum Discussion
Trouble updating Crossplane Claim status with Equinix Provider
I’m having some trouble using the Equinix providers within a Claim and I’m not sure where the problem lies. The issue is that I am trying to take the ID uuid from the Device status.atProvider.id and update a status.id field in my xrd claim, but the status never seems to get updated. This works fine with the AWS provider as an example.
In my example I want to grab the UUID of the device and populate the Claim XRD's status.id field, but I do not see this population happening. I use the same technique with the upbound AWS provider so I know it is valid.
Within the composition.yaml:
2 Replies
Looks like the error may have been related to some typos in my composition/definition yaml files. The Crossplane linter could not catch these specific ones, but after refactoring both these files I do now see the xrd status fields being populated with the right info. Thanks Marques.
These crossplane providers are invaluable and I hope more development can occur so we can better integrate with Equinix.
I'll try this myself in the Equinix Crossplane provider's 0.6.1 release with the latest Crossplane and see where I end up.
In a now deprecated Equinix Metal specific provider, I built a conformance testing XRD: https://github.com/cncf/crossplane-conformance/pull/22/files#diff-21d692ae5f5d0069c68cd54654e79d61dfc36eda5a7858cb681a7f772def70da
This took advantage of cross-resource selectors and references, features that have semantically changed in newer cross-plane versions.
Featured Places
Discussions
Engage with industry experts, share insights, ask questions, and grow your network.Ideas
We're listening! Submit your ideas to shape the future of Equinix!Groups
Ready to collaborate? Join a Group or upcoming beta program.What's New
Stay ahead with the latest from Equinix. Discover new product announcements, insightful tutorials, and practical use cases.Events
Your Guide to Upcoming Events - Online, Hybrid, and In-Person!
