-
Notifications
You must be signed in to change notification settings - Fork 24
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
Tfautomv does not perform the ignore completely #86
Comments
Thanks for reaching out! Your issue touches on a lot of things and I'll try to address them all :) Originally we added the However, even if a new flag allowed As you mentioned in your issue, if All that being said, I'd like to find a solution to your problem. If in your use-case it's possible to first reorganize resources without changing their attributes, then run If that isn't possible, then I'd like to better understand the sort of differences in attributes that |
Hi @RonaldoDS27, thanks for sharing more details! In this particular case, it's pretty clear what moves
but the resources planned for deletion do not. In the short-term, I'd say you have two options:
Let me know what option you decide on and what the result is :) Your situation points to multiple ways we could improve The first is that The second is that the
The third is that it would be convenient to be able to tell |
First of all, thank you very much for this tool, it makes the process of automating the TF Move much easier.
The "Problem" we currently have is the following.
We are running the tool, in order to detect the changes in iaC modules that we have altered, however, our iac plan, gives us a total of 41 Destroys and 42 Creates, which translates to 41 terraform state moves.
Plan: 42 to add, 9 to change, 41 to destroy.
We identified that it is for some parameters that it cannot move, nevertheless, we have created a Script that automatically detects those parameters for which it cannot move the resource, and by means of that script, we constructed the ignore with which the tfautomv would be executed, that is to say, something like this: tfautomv --ignore="everything:aws_instance:credit_specification.#" --ignore="everything: aws_rds_cluster: availability_zones.#"
However, it is not doing the process to ignore them, so we always get a lower number in the state moves.
33 moves written to moves.tf
.Additionally, it was evidenced that when having 1,2,3,...(or higher) Matches in the resources, it omits the creation of state move
│ 3 matches for module.backend.module.apigw_keys.aws_api_gateway_usage_plan_key.this[1] (delete) in current directory
│ │ module.backend.module.apigw_keys.aws_api_gateway_usage_plan_key.this["plan-test-1"] (create) in current directory
│ │ module.backend.module.apigw_keys.aws_api_gateway_usage_plan_key.this["plan-test-2"] (create) in current directory
│ │ module.backend.module.apigw_keys.aws_api_gateway_usage_plan_key.this["plan-test-3"] (create) in current directory
.We would like to know, if it is possible that from the functionality of the same tool, you can add a feature, through which you can perform a complete ignore on all resources that are being detected as changing, because in fairly large infrastructures, can run only 50% in the terraform state move.
I appreciate your support and response.
The text was updated successfully, but these errors were encountered: