Closed seanyoungberg closed 3 years ago
The problem is that I added a new ForceNew: true
param in both directions (device_group
from the NGFW's perspective, vsys
from Panorama's perspective), and Terraform is interpreting this as a change that requires redeploying the config.
Working on finding a solution.
Ok, I think I've fixed this. Please check out v1.7.1 of the provider. There are now migrate state functions that should deal with this.
@seanyoungberg
Does 1.7.1 / 1.8 fix the issue for you?
@shinmog Yes, indeed. Works fine on 1.8. Recently got confirmation from someone that initial discovered this on a more complex code / state. Thanks for the super-quick turnaround!
Describe the bug
After upgrading to 1.7.0, having some issues with panos_panorama_address_object. The objects are forcing recreation which then causes an error with the NAT policies that are referencing those objects.
Expected behavior
Address object should not be recreated when moving to 1.7.0 provider
Current behavior
When running apply with 1.7.0 against state that was previously deployed with 1.6.3, the address objects are attempted to be replaced. There is a NAT policy referencing this object so the apply fails as the address object cannot be deleted since it is still being referenced.
Possible solution
Tried with create before destroy lifecycle on the address object, which seemed to succeed in create a new object, but subsequent apply tried to destroy the "deposed object" and still had same error with reference from NAT policy
Steps to reproduce
First execute this with 1.6.3 provider and then run again with 1.7.0 provider.
Context
Caused confusion and time spent troubleshooting. For now reverted back to 1.6.3.
Your Environment
Tested with tf 13.5 and 14.x