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
The environment based personal_access_token is re-evaluated during the apply phase.
But the system.access token changes per job, so they don't match anymore when the apply is in a another job/stage.
# plan
AZDO_PERSONAL_ACCESS_TOKEN=abc terraform plan -out plan.bin
# apply
AZDO_PERSONAL_ACCESS_TOKEN=other terraform apply plan.bin
# or
terraform apply plan.bin
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for
│ databricks_git_credential.ado
│ to include new values learned so far during apply, provider
│ "registry.terraform.io/databricks/databricks" produced an invalid new value
│ for .personal_access_token: inconsistent values for sensitive attribute.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
I think the input for the apply stage should not be dependent on environment settings anymore. The Plan phase stored the sensitive secret already in the plan file.
The text was updated successfully, but these errors were encountered:
The environment based personal_access_token is re-evaluated during the apply phase.
But the system.access token changes per job, so they don't match anymore when the apply is in a another job/stage.
Feature implemented #1352.
reproduce
Usage example
I think the input for the apply stage should not be dependent on environment settings anymore. The Plan phase stored the sensitive secret already in the plan file.
The text was updated successfully, but these errors were encountered: