-
Notifications
You must be signed in to change notification settings - Fork 459
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
CDKTF diff & deploy want to delete every resource and create identical ones with new names after upgrade from 0.16.1 to 0.17.3 #3114
Comments
It appears to be a naming schema change forced instead by 17.0. We were used to breaking changes being listed in the release descriptions here: https://github.com/hashicorp/terraform-cdk/releases Is there an upgrade guide for the change? #2937
The upgrade guide w/ the release just tells me that some keys are useless now but doesn't tell me how I can fix the stack states. |
#2954 lists a couple options on how to transition. |
We'll add additional documentation to help migrate soon. |
Was it added somewhere? |
I was just testing 0.19.2 with our code, and it seems it doesn't work with cc @Maed223 , author of the PR. |
Hi @mhaligowski 👋 Unfortunately, we don't yet support the moved block for modules which makes it impossible to add this to the Aspect. However, I created #3432 which will print a warning with instructions with a manual |
Closing this as #3432 is merged now 👍 |
I'm going to lock this issue because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Expected Behavior
Our deploys and diffs should work the way they used to or breaking changes should have documentation and upgrade instructions.
Actual Behavior
We upgraded from 0.16.1 to 0.17.3 and now every resource has a diff.
Resource names went from (as an example where my stack name is auth_staging)
authstaging_nikeauthserviceappmemcacheinstance_C0A1A76C
tonike_auth_service_app_memcache_instance
I think this is the cause (#2956)
Steps to Reproduce
Our environment has multiple stacks -- so synth & deploy with 0.16.1, upgrade to 0.17.3 and deploy.
Versions
Providers
Gist
No response
Possible Solutions
No response
Workarounds
No response
Anything Else?
No response
References
Help Wanted
Community Note
The text was updated successfully, but these errors were encountered: