Hi all,
PureCloudPlatformClientV2 presented us with a nearly identical scenario back in 2021 during a large-scale knowledge migration. We’d spent a month chasing a ghost where the state file wouldn’t align with the actual environment, eventually finding that certain metadata fields were being ignored by the provider. It felt like a solved problem, but the same pattern is resurfacing now. We’ve hit a wall where the cxascode provider is flagging a permanent drift on knowledge documents, even though no changes were made to the source files.
The terraform plan shows a perpetual diff on the document resource. It’s triggering a replace action every single time we run the pipeline. We’ve tried to manually refresh the state and checked the GET /api/v2/knowledge/knowledgebases/{knowledgeBaseId}/documents/{documentId} response to see if the return payload differs from the terraform configuration. The attributes match, yet the provider refuses to settle. This broke our deployment pipeline for six hours this morning.