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
Normally, if you create drift by removing a resource from the deployed infrastructure, Terraform will try to re-create the resource as it is still specified in the state.
This is not the case with the token resource in this provider.
E.g. if i delete a Token, which was created using Terraform, I get the following error:
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: Unable to read token
│
│ with axiom_token.axiom_token_analytics_prod,
│ on cdk.tf.json line 227, in resource.axiom_token.axiom_token_analytics_prod:
│ 227: },
│
│ API error 404: Not Found
╵
This can be worked around by removing the resource from the state first using terraform state rm axiom_token.axiom_token_analytics_prod.
The text was updated successfully, but these errors were encountered:
Normally, if you create drift by removing a resource from the deployed infrastructure, Terraform will try to re-create the resource as it is still specified in the state.
This is not the case with the token resource in this provider.
E.g. if i delete a Token, which was created using Terraform, I get the following error:
This can be worked around by removing the resource from the state first using
terraform state rm axiom_token.axiom_token_analytics_prod
.The text was updated successfully, but these errors were encountered: