Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plan: Invalid -out Flag Note for VCS Connection Cloud Backend #35301

Open
bflad opened this issue Jun 6, 2024 · 0 comments
Open

plan: Invalid -out Flag Note for VCS Connection Cloud Backend #35301

bflad opened this issue Jun 6, 2024 · 0 comments
Labels
bug new new issue not yet triaged v1.8 Issues (primarily bugs) reported against v1.8 releases

Comments

@bflad
Copy link
Contributor

bflad commented Jun 6, 2024

Terraform Version

Terraform v1.8.5
on darwin_arm64

Terraform Configuration Files

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

  1. Create VCS connected cloud backend
  2. terraform init
  3. 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

@bflad bflad added bug new new issue not yet triaged labels Jun 6, 2024
@apparentlymart apparentlymart added the v1.8 Issues (primarily bugs) reported against v1.8 releases label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug new new issue not yet triaged v1.8 Issues (primarily bugs) reported against v1.8 releases
Projects
None yet
Development

No branches or pull requests

2 participants