Document how to change provider registries #984
Conversation
✅ Deploy Preview for crossplane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
negz
force-pushed
the
switcheroo
branch
2 times, most recently
from
6580860 to
63f7ceb
Compare
negz
changed the title
Add guide for safely changing providers between compatible packages in different OCI registries (e.g., upbound → crossplane-contrib). The guide focuses on the manual coordination approach needed when providers have family dependencies that create ownership conflicts. Includes step-by-step process, troubleshooting, and rollback procedures. Also adds cross-reference from the upgrade-to-v2 guide for users switching registries during their v2 upgrade. Signed-off-by: Nic Cope <nicc@rk0n.org>
|
I realized there's a simpler approach:
In simple tests this seems to work fine. |
I've tested it and it works, but it feels like it's dependent on a shortcoming in the package manager. I'd expect that the dependent packages would attempt to self-heal by reinstalling their dependency once it's gone. So:
Step 3 doesn't happen though, because the package manager only solves and installs dependencies at package install time. If the dependencies are removed after the package is installed, the packages just start saying they're unhealthy and missing deps. So I'm hesitant to document this simpler approach, because it won't work if we improve the package manager's self-healing of dependencies. |
1 participant
This PR adds a guide for safely changing providers between compatible packages in different OCI registries (e.g., upbound → crossplane-contrib).
The guide focuses on the manual coordination approach needed when providers have family dependencies that create ownership conflicts. Includes step-by-step process, troubleshooting, and rollback procedures.
Also adds cross-reference from the upgrade-to-v2 guide for users switching registries during their v2 upgrade.