Hi all,
Is there a recommended pattern for updating boolean variables within Architect flows via Terraform? It’s a familiar story - we’ve hit a strange state drift issue, and it feels like a regression from something we resolved back in 2021. We’re deploying changes to a production environment and seeing the variable values revert after the Terraform apply completes. Specifically, toggles in a flow - a simple true/false switch controlling whether a transfer action executes - are consistently flipping back to their original state. The flow in question is relatively straightforward: a simple IVR routing flow with a conditional transfer based on the variable transferEnabled.
PureCloudPlatformClientV2 doesn’t seem to fully propagate the boolean value through the /api/v2/architect/flows/{flowId}/variables/{variableId} endpoint when updating via Terraform. It’s almost as if the API expects a string representation, even though the schema defines it as a boolean. We’ve been attempting to set the value using "true" and "false" as strings, but that doesn’t prevent the drift. We initially encountered a similar issue with numeric variables years ago, and the resolution involved ensuring strict schema adherence in the Terraform configuration. The current Terraform configuration for the variable is: type = "boolean". We’ve also tried explicitly casting the variable to a string with type = "string" and using "true" as a value, but the drift continues. The flow ID is 6789abcdef0123456789abcdef01 and the variable ID is 1234567890abcdef1234567890. It’s… perplexing.