terraform state rm ignores -state=... option

[dlamotte]

Terraform Version

Terraform v0.9.8

Terraform Configuration Files

terraform {
  backend "s3" {
    bucket     = "mybucket"
    encrypt    = true
    key        = "prod.tfstate"
    lock_table = "terraform"
    region     = "us-west-1"
  }
}

provider "aws" {
    region = "us-west-1"
}

Debug Output

None

Panic Output

None

Expected Behavior

State within the provided -state=... file should have been updated.

Actual Behavior

State provided in the remote s3 backend terraform block above was updated and the local -state=... provided with the option was backed up but not the state in the remote bucket.

Steps to Reproduce

1. Write above terraform block with remote backend s3 state to a terraform file.
2. terraform state pull > dev.tfstate
3. terraform state rm -state=./dev.tfstate aws_iam_group.mygroup

Data-loss (IMO): dev.tfstate is backed up to dev.tfstate.backup.* BUT remote state in the bucket is updated(!!!). We have s3 bucket object versioning on, so we just reverted without issue, but its not clear whether this is a backend issue or something higher in which it could be very scary very fast.

Important Factoids

Standard AWS + S3

References

Nope

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.