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
Add crossplane.io/paused annotation and deletionPolicy: Orphan on all community managed resources
Shift all managed resources to the official provider.
In the Git repository, update the composition but keep the order and spec.resources[].name unchanged.
Apply the updated composition.
The composition will detect all new resources and update resourceRefs[].apiVersion and resourceRefs[].Kind in the XR, while the resource names remain the same.
Remove all community managed resources from the community AWS provider.
This process worked with Crossplane version v1.13.x but encountered issues starting with versions v1.14.x/v1.15.x. The error message encountered is:
cannot compose resources: cannot parse base template of composed resource 'iam': cannot change the kind or group of a composed resource from iam.aws.crossplane.io/v1beta1, Kind=Role to iam.aws.upbound.io/v1beta1, Kind=Role (possible composed resource template mismatch)
The change in behavior with Crossplane versions v1.14.x and v1.15.x raises questions, especially since migrating to the official provider is a common use case.
What happened?
We're working on moving our resources from the community AWS provider (https://github.com/crossplane-contrib/provider-aws) to the official Upbound AWS provider (https://github.com/upbound/provider-aws).
Here's a brief overview of the steps involved:
crossplane.io/paused
annotation anddeletionPolicy: Orphan
on all community managed resourcesorder
andspec.resources[].name
unchanged.resourceRefs[].apiVersion
andresourceRefs[].Kind
in the XR, while the resource names remain the same.This process worked with Crossplane version
v1.13.x
but encountered issues starting with versionsv1.14.x
/v1.15.x
. The error message encountered is:The change in behavior with Crossplane versions
v1.14.x
andv1.15.x
raises questions, especially since migrating to the official provider is a common use case.change of the behavior implemented with: #4500
recent change for version updates: #5369
discussion between @phisco and @turkenh #5369 (comment)
How can we reproduce it?
https://github.com/haarchri/xp-issue-5473
What environment did it happen in?
Crossplane version: v1.14.6-up.1, v1.15.0-up.1
The text was updated successfully, but these errors were encountered: