You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have configured the Microsoft Entra ID connector with Terraform. The pipeline to (re-)deploy this connector runs on a weekly schedule to update the secret, which is frequently rotated. The output of terraform plan shows that the secret should update, but is in fact not updated which leads to the connector failing to connect when the previous secret expires.
When I manually copy the client secret from the AWS secret and paste it into the Fivetran UI, the connector resumes successfully.
Describe the bug
We have configured the Microsoft Entra ID connector with Terraform. The pipeline to (re-)deploy this connector runs on a weekly schedule to update the secret, which is frequently rotated. The output of
terraform plan
shows that the secret should update, but is in fact not updated which leads to the connector failing to connect when the previous secret expires.When I manually copy the client secret from the AWS secret and paste it into the Fivetran UI, the connector resumes successfully.
To Reproduce
Expected behavior
The secret being updated with the new value.
Logs & Output
Notice that
client_secret
is the only attribute being changed in theconfig
block, which is the only updated value in the AWS secret.Plugin version:
Terraform: 1.9.8
Fivetran provider: 1.4.2.
The text was updated successfully, but these errors were encountered: