Description
This only applies if you are using the genesyscloud_flow resource in your CX as Code deployments.
A defect was encountered in the genesyscloud_flow resource that could inadvertently deploy a flow when a terraform plan or terraform destroy is executed.
The defect was fixed in version v1.8.0 or higher of the the CX as Code provider. If you are using a version lower than version 1.8.0 it is highly recommended you upgrade to version 1.8.0 or higher.
Please note, that with the v1.8.0 release of the CX as Code provider, the genesyscloud_flow resource you must set the file_content_hash attribute. This field was formerly optional, but it is now required. Please see the genesyscloud_flow resource documentation (Terraform Registry) for details on how to set this atribute.
Change Category
CX as Code
Change Context
A defect was encountered in CX as Code that could cause a flow deployment even if the user issues a terraform plan or terraform destroy.
Change Impact
This only impacts genesyscloud_flow users in CX as Code. Customers will need to upgrade their CX as Code resource and use the file_content_hash attribute. Previously this field was optional.
Date of Change
Oct 31, 2022
Impacted APIs
No direct API impact
References
[DEVENGAGE-1472]