Closed bobh66 closed 1 year ago
When migrating from terrajet to upjet a new configuration option is required to maintain the existing API root group, for example:
config.WithRootGroup('foo.crossplane.io')
is required to continue to use the foo.crossplane.io API group.
foo.crossplane.io
The default is to use upbound.io for the root group.
upbound.io
Follow the migration guide for a non-upbound.io resource and observe that the API root group changes to upbound.io when the new resource is generated.
@bobh66 this is now configurable in our upjet-provider-tenmplate https://github.com/upbound/upjet-provider-template/pull/50
upjet-provider-tenmplate
What happened?
When migrating from terrajet to upjet a new configuration option is required to maintain the existing API root group, for example:
is required to continue to use the
foo.crossplane.io
API group.The default is to use
upbound.io
for the root group.How can we reproduce it?
Follow the migration guide for a non-upbound.io resource and observe that the API root group changes to upbound.io when the new resource is generated.