Closed csantanapr closed 1 week ago
@csantanapr there is a manual migration guide available here: https://docs.upbound.io/knowledge-base/migrate-to-provider-families/
And we are in the final stages of polishing up a tool to automate the migration: https://github.com/upbound/docs/pull/174/files
/cc @sergenyalcin for the feedback on things to consider /cc @turkenf let's update the README with information on the provider family architecture.
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale
. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale
. If you still need help, feel free to comment or reopen the issue!
What problem are you facing?
The README.md doesn't mention provider families
Document a guide that covers steps and considerations when migrating from monolith provider to provider families
Things to consider:
provider-aws-*
in provider family be more specificprovider-aws-ec2-*