packer push does not push variables

[clstokes]

The packer documentation says that users should be able to push variables with packer push -var "var=val ..., however this doesn't seem to work. Turning on Packer's log with PACKER_LOG=1, shows that no variable information is in the request payload to Atlas.

Log output and example Packer config are at https://gist.github.com/clstokes/148b682b196ff62643eb.

I've tested this with both Packer v0.8.1 and v0.8.5. Both exhibit the same behavior.

[cbednarski]

Thanks for submitting this. I've run into this as well but I have not yet tracked down where the flags are getting lost.

[clstokes]

It looks like this when trying to pass a variables file with the -var-file parameter too, but also seems like there's not a way to run Packer in Atlas with an external JSON file?

[cyberswat]

I'm hitting this as well using packer 0.8.6 against Atlas. Everything works as intended locally.

[clstokes]

terraform push doesn't push AWS keys if they're being inherited from the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables. Packer should probably follow this behavior.

[bascht]

At the moment I've worked my way around this by setting all required variables manually in the Atlas Build config and then just using {{ env }} - what's a bit confusing: The Build tab has a variables section that are entirely environment variables, while the Infrastructure tab combines both terraform variables _and_ environment variables in that tab. :)

[AirbornePorcine]

+1, this is basically preventing us from using Atlas with Packer as we have a number of dynamic variables that need to be pushed up for each build.

[domofactor]

+1, just bumped into this issue as well. any updates on a fix for this?

we're pushing to Atlas from Wercker CI. So, as a workaround we're just throwing in some regex before pushing like so:

sed -i 's/DOCKER_TAG/$WERCKER_GIT_COMMIT/' packer.json && packer push packer.json

[cybertk]

Same issue here on Travis with packer 0.8.6

[gamename]

+1
Still happening with packer 0.10.0

[gamename]

Any ETA? Been running into this for 6+ months.

Guys, this is not an obscure use case. It is clearly documented functionality that simply does not work. How can I convince my management to work with (and spend money on) Hashicorp when problems like this go unaddressed?

@sethvargo @kikitux @mitchellh @armon

[dynamike]

Yet another request for this

[cbednarski]

Hey folks, thanks for your interest in this feature. It is in progress but unfortunately I don't have an ETA to share with you.

[benpriestman]

+1

[denniswebb]

Just hit this issue myself. Version 0.10.1

[kenfusion]

In the mean time, can you take it out of documentation? I was spinning wheels for days until I found this discussion.

[mo-mughrabi]

Hitting this issue too, is there an API or alternative we could use meanwhile to push environment variables to builds? as its unpractical in our case to run 20+ builds and have to go one by one and update environment variables :/

[cyberswat]

@mo-mughrabi This issue is why we chose to never to use Hashicorp's enterprise offerings. This has been a known issue for more than a year. It's a big deal because it stops legitimate use, and the workarounds are not practical.

[mwhooker]

should be fixed now