Failed to configure remote backend "atlas" when migrate to 0.9

[dot]

Terraform Version

Terraform v0.9.0

Steps to Reproduce

in v0.8.8
terraform remote config -backend="atlas" -backend-config="name=my/atlas"

Then, bump terraform to v0.9.0

And, add this configuration.

terraform {
  backend "atlas" {
    name = "my/atlas"
  }
}

and run terraform init

Actual Behavior

# terraform init
Downloading modules (if any)...
Get: ....... 
Get: .......
Initializing the backend...
Legacy remote state was detected!

Terraform has detected you still have legacy remote state enabled while
also having a backend configured. Terraform will now ask if you want to
migrate your legacy remote state data to the configured backend.


Do you want to copy the legacy remote state from "atlas"?
  Terraform can copy the existing state in your legacy remote state
  backend to your newly configured backend. Please answer "yes" or "no".

  Enter a value: yes


One or more errors occurred while configuring the legacy remote state.
If fixing these errors requires changing your remote state configuration,
you must switch your configuration to the new remote backend configuration.
You can learn more about remote backends at the URL below:

TODO: URL

The error(s) configuring the legacy remote state:

Failed to configure remote backend "atlas": unknown remote client type: atlas

State file

after run terrafrom init tfstate file is

{
    "version": 3,
    "terraform_version": "0.8.8",
    "serial": 77,
    "lineage": "xxxxxxx",
    "remote": {
        "type": "atlas",
        "config": {
            "name": "my/atlas"
        }
    },
    "backend": {
        "type": "atlas",
        "config": {
            "name": "my/atlas"
        },
        "hash": (xxx)
    },
..................

[mitchellh]

Thanks, fixed in PR :)

[ghost]

I don't think this is working. Here is the problem I am running into:

having problem using atlas as a backend with terraform 0.9.3
added the following config terraform {
required_version = ">= 0.9.0"
backend "atlas" {
name = "romildo/aws-global"
}
}
run terraform init which was a success Initializing the backend...
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your environment. If you forget, other
commands will detect it and remind you to do so if necessary.
but when running terraform push it keep asking to run init again
romildo@bigbear:~/RubymineProjects/terraform-best-practices/terraform/providers/aws/global$ terraform push -name $ATLAS_USERNAME/aws-global -var "atlas_token=$ATLAS_TOKEN" -var "atlas_username=$ATLAS_USERNAME" ../../../../terraform/
Backend reinitialization required. Please run "terraform init".
Reason: Unsetting the previously set backend "atlas"
The "backend" is the interface that Terraform uses to store state,
perform operations, etc. If this message is showing up, it means that the
Terraform configuration you're using is using a custom configuration for
the Terraform backend.
Changes to backend configurations require reinitialization. This allows
Terraform to setup the new configuration, copy existing state, etc. This is
only done during "terraform init". Please run that command now then try again.
If the change reason above is incorrect, please verify your configuration
hasn't changed and try again. At this point, no changes to your existing
configuration or state have been made.
Failed to load backend: Initialization required. Please see the error message above.
any ideas what is the problem?????

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