Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure resources are in the correct module #5168

Open
corymhall opened this issue Feb 5, 2025 · 1 comment
Open

Ensure resources are in the correct module #5168

corymhall opened this issue Feb 5, 2025 · 1 comment
Labels
7.0 impact/breaking Fixing this issue will require a breaking change kind/enhancement Improvements or new features

Comments

@corymhall
Copy link
Contributor

There are some resources where we have diverged from Terraform in how we organize the resources into modules. For example, Terraform has the EC2, Vpc, & Vpc IPAM modules and we have the EC2 & Vpc modules. Even then our resources are not organized into the EC2 and Vpc modules the same way that Terraform has organized them.

To make this easier on users we should make sure our organization matches how Terraform is organized. This will require a breaking change so should wait until the next major release.

@corymhall corymhall added 7.0 impact/breaking Fixing this issue will require a breaking change kind/enhancement Improvements or new features labels Feb 5, 2025
@t0yv0
Copy link
Member

t0yv0 commented Feb 13, 2025

We might have an option to effect a non-breaking change via "source aliases" whereby old classes are retrained in SDK as-is but new classes are added at the correct location, and both classes point to the same underlying resource token (that's changing). It would increase SDK sizes. I think absent concrete interest in this I would wait until 7.0 indeed as you suggest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7.0 impact/breaking Fixing this issue will require a breaking change kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants