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

backend consul problem with address flag #1392

Closed
kennyg opened this issue Apr 4, 2015 · 5 comments
Closed

backend consul problem with address flag #1392

kennyg opened this issue Apr 4, 2015 · 5 comments
Assignees

Comments

@kennyg
Copy link

kennyg commented Apr 4, 2015

with v0.3 I used to upload the state with:

terraform remote -backend=consul -address=consulhost:8500 -path=release_engineering/terraform/terraform-docker

now with v0.4 and the new remote config command:
terraform remote config -backend='consul' -address='consulhost:8500' -path='release_engineering/terraform/terraform-docker'

I get an error with the help text:
Error parsing CLI flags: flag provided but not defined: -address

@hairmare
Copy link

hairmare commented Apr 4, 2015

I just ran into this as well. You need to specify the -address flag as follows.

-backend-config="address=consulhost:8500"

The docs probably need updating for v0.4.

@kennyg
Copy link
Author

kennyg commented Apr 6, 2015

I tried what @hairmare suggested and the remote command didn't recognize the -path argument. I added -backend-config='path=release_engineering/terraform/terraform-docker' and it errors with:
Error initilizing remote state:
It seems I should migrate the 0.3 remote consul state to local storage before upgrading to 0.4 and setting up the remote config.

@phinze phinze added the core label Apr 7, 2015
@phinze
Copy link
Contributor

phinze commented Apr 7, 2015

Thanks for the report @kennyg - @mitchellh can you pick this up in your remote-state issue sweep?

@mitchellh mitchellh added the bug label Apr 7, 2015
@mitchellh mitchellh self-assigned this Apr 7, 2015
mitchellh referenced this issue Apr 7, 2015
reflect.DeepEqual was returning false, sometimes.
@mitchellh
Copy link
Contributor

Fixed

@ghost
Copy link

ghost commented May 3, 2020

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.

@ghost ghost locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants