terraform-provider-bigip: `bigip_as3` resource `resourceBigipAs3Read` action does not store actual value in state
It doesn’t appear that the resourceBigipAs3Read function is currently detecting and writing the actual current AS3 declaration into state.
According to https://www.terraform.io/docs/extend/best-practices/detecting-drift.html it looks like it should be setting d.Set("as3_json", <filtered as3 declaration from http request>)
As I’ve been utilizing the resource, I’ve had scenarios where I had issues with the syntax so the actual HTTP POST with the AS3 declaration failed, but since Read does not pull the actual values back, it simply wrote my errored declaration into state, so subsequent executions “saw” no change despite the declaration on the remote appliance not matching my local.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 16 (1 by maintainers)
Fixed in v1.2.0
Thanks for the info @zx1986 . This is part of what is being fixed in the upcoming release.
Understood. I guess what I am asking is it safe to use version 1.1.2 until those updates are released. Trying to understand current impact in 1.1.2 if it adds all as3 declarations to state file.Answered my own question. It deleted all as3 tenants outside of the one being applied. This is really concerning.