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

Prefer Atlas variables over local variables #2373

Closed
sethvargo opened this issue Jun 16, 2015 · 1 comment · Fixed by #2559
Closed

Prefer Atlas variables over local variables #2373

sethvargo opened this issue Jun 16, 2015 · 1 comment · Fixed by #2559
Assignees

Comments

@sethvargo
Copy link
Contributor

This issue comes from our discussion today. The UX for terraform push with respect to variables should be the following:

  • On the first terraform push, all local variables are sent and stored in Atlas

  • On subsequent terraform push, only local variables that have not yet been stored in Atlas are sent

    • A warning should be displayed telling the user that only new variables are added
  • A new CLI option/flag should be added that allows the user to update 1+ remote terraform variables via the command line as part of terraform push, something like:

    $ terraform push -var="num-nodes=5"

    This will always overwrite (or create) the remote terraform variable in Atlas

/cc @pearkes @mitchellh

@mitchellh mitchellh self-assigned this Jun 29, 2015
mitchellh added a commit that referenced this issue Jun 29, 2015
command/push: new UX (prefer Atlas over local vars) [GH-2373]
@ghost
Copy link

ghost commented Aug 16, 2019

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 Aug 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants