Open t3mi opened 2 years ago
I have the same "problem" and always end up me doing a terraform apply targeting the caf resource.
This will be changed in verseion 3.0 it should be released in the comming weeks if not days :)
This still seems to be an issue.
Any news on when it is expected to be fixed?
Any updates here? Would be nice if the referenced PR could be merged..
Same issue here, any updates on this? Thanks!
be changed in version 3.0 it should be released in the coming weeks
Will this be backported to 1.x stream?
I'm using single resource
azurecaf_name
withresource_types
limited to the ones required by module. When new resource is added andresource_types
updated to include the new type - terraform triggers to recreate everything, even already deployed resources. Any chance such behavior could be changed to allow updates to the property?