Trying to make sense of why the genesyscloud_oauth_client resource fails during terraform plan with a 409 Conflict when attempting to bind custom scopes to a standard role via HCL. The provider v1.82.0 expects explicit scope mapping, but the API returns a validation error stating the scope is already implicitly granted through role hierarchy.
Running this in EU1 environment. The deployment pipeline hangs because Terraform detects a perpetual state drift on the scopes attribute despite the API accepting the configuration manually. Is there a specific configuration block or ignore_lifecycle rule required to suppress this false positive drift detection for inherited permissions?