In our existing infra, we calling version 7.4.0 of the following module in our own module.
terraform-google-modules/vm/google//modules/instance_template
When we try and upgrade to latest version 11.1.0, some new attributes like enable_nested_virtualization, total_egress_bandwidth_tier are getting added which are forcing the resource replacement(destroy and create).
Is there a way to handle these new attributes so that they don’t force replacement? Also, these new attributes are optional as per the module documentation but still they’re getting added.
We tried adding these new attributes to terraform code and then run the plan, but as these are new attributes, we’re still getting force replacement message.
inpuram is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.