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
terraform {
cloud {
organization="..."workspaces {
name="..."
}
}
}
# any other configuration should do it
Debug Output
I don't think it's applicable, but can provide if needed.
Expected Behavior
Terraform CLI local output does not offer invalid note/advice about -out flag for VCS connected workspaces. A small text update would be more than okay, e.g.
$ terraform plan...─Note: This was a speculative plan for a VCS connected workspace. Terraform cannot guarantee to take exactly these actions if you plan again.
Actual Behavior
$ terraform plan...─Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
$ terraform plan -out=test.tfplan╷│ Error: Saved plans not allowed for workspaces with a VCS connection││ A workspace that is connected to a VCS requires the VCS-driven workflow to ensure that the VCS remains the single source of truth.╵
I fully understand why this is occurring, its just that the note is just not tailored for the practitioner situation and suggesting an invalid action.
Steps to Reproduce
Create VCS connected cloud backend
terraform init
terraform plan
Additional Context
Noticed while trying to debug a missing error diagnostic issue that only seems to occur in HCP Terraform. The -out plan file seems like it would be helpful for what I think is going on, but understandable its not returnable for this type of setup.
References
No response
The text was updated successfully, but these errors were encountered:
Terraform Version
Terraform Configuration Files
Debug Output
I don't think it's applicable, but can provide if needed.
Expected Behavior
Terraform CLI local output does not offer invalid note/advice about
-out
flag for VCS connected workspaces. A small text update would be more than okay, e.g.Actual Behavior
I fully understand why this is occurring, its just that the note is just not tailored for the practitioner situation and suggesting an invalid action.
Steps to Reproduce
cloud
backendterraform init
terraform plan
Additional Context
Noticed while trying to debug a missing error diagnostic issue that only seems to occur in HCP Terraform. The
-out
plan file seems like it would be helpful for what I think is going on, but understandable its not returnable for this type of setup.References
No response
The text was updated successfully, but these errors were encountered: