While running through the getting-started examples, I ran into a strange
error:
packer $ packer validate example.json
Failed to parse template: Error in line 16, char 2: invalid character
'"' after object key:value pair
"provisioners": [{
packer $
The error was not immediately obvious, as this is my first time working
with Packer, and like many users this also happens to be my first time
working with JSON.
Solution:
I was missing a comma after the 'builders' configuration. I'm sure this
is a common problem, so let's specifically mention that in the document.
While running through the getting-started examples, I ran into a strange
error:
packer $ packer validate example.json
Failed to parse template: Error in line 16, char 2: invalid character
'"' after object key:value pair
"provisioners": [{
packer $
The error was not immediately obvious, as this is my first time working
with Packer, and like many users this also happens to be my first time
working with JSON.
Solution:
I was missing a comma after the 'builders' configuration. I'm sure this
is a common problem, so let's specifically mention that in the document.
As per https://github.com/mitchellh/packer/issues/1142, it's critical to add openstack_provider: rackspace in order to get anything to work reliably with Rackspace and Packer in 6.0.
Question: should the openstack_provider field now be marked as required?
before, this code had joining path elements by filepath module. filepath module generate path string with backslash-joined in Windows. but ESX require path string with slash-joined. it means that this code generate illegal path string in windows. illegal path string raised "Error creating disk".
this patch fixes path separator from backslash to slash in windows. from this, creating disk would succeed without error.
[gophercloud#168](https://github.com/rackspace/gophercloud/issues/168) has been
patched to not panic on non-existing server id's. If an error is returned,
check if the error is a 404 first before bailing.
With go tip, the output from Artifact.String will sometimes be output in a
different order than the tests. Sort the AMI strings before outputting.
See https://travis-ci.org/mitchellh/packer/jobs/28748467 for an example of this
failure.
Mitchell Hashimoto
Sudharshan S
stefanlasiewski
Kane Rogers
Tehmasp Chaudhri
Misha Brukman
Florian Noeding
Ross Smith II
Hiroaki Nakamura
Jack Pearkes
sawanoboly
yuuzi41
Ian Delahorne
Ian Delahorne