Allow configurable keyEnvPrefix

[voltechs]

Terraform Version

0.9.2

Affected Resource(s)

remote state backend (s3)

Terraform Configuration Files

terraform {
	required_version = ">= 0.9.2"
	backend "s3" {
		bucket = "platform-infrastructure"
		key = "environments/alpha/master.tfstate"
		region = "us-west-2"
	}
}

Expected Behavior

I expect not to be forced into some hand-held path by a tool (terraform) for advanced users (anybody who uses terraform).

Read: let me configure keyEnvPrefix. I've already created my own bucket, and nested my environment files under /environments/{environment}/master.tfstate

Actual Behavior

My states are stored and pulled from `platform-infrastructure/env:/alpha/environments/alpha/master.tfstate

The first alpha originating from terraform env, and the second alpha comes from my own (legacy) namespacing. (We're migrating from self-managed environments to TF managed)

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Try to use terraform with an S3 backend

[gmetzker]

I agree. This would be nice if there was more flexibility with how this key prefix works when using multiple environments.

[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.