18 Commits (97f3f31d3db94de8005c6095269e4ec881c40a9a)

Author	SHA1	Message	Date
Chris Bednarski	1a775c05d9	Update calls to amazon to match the upstream ... - see http://aws.amazon.com/releasenotes/2948141298714307 - run awsmigrate-renamer on each amazon module (chroot, instance, etc.)	11 years ago
Chris Bednarski	abb67fdd79	Fix govet issues	11 years ago
Mitchell Hashimoto	be4a82dfae	amazon/*: fix some merge conflicts	11 years ago
Mitchell Hashimoto	8e1db0d94c	Merge branch 'fix_amazon_instance_waits' of https://github.com/renat-sabitov/packer into renat-sabitov-fix_amazon_instance_waits	11 years ago
Seth Vargo	33ca8b7fb5	Migrate to new AWS repo	11 years ago
Mitchell Hashimoto	913d6f6996	builder/amazon/common: fix compilation issues with latest libs	11 years ago
James Nugent	e99cd56b6c	Migrate from mitchellh/goamz to awslabs/aws-sdk-go ... This commit moves the Amazon builders of Packer away from the Hashicorp fork of the goamz library to the official AWS SDK for Go, in order that third party plugins may depend on the more complete official library more easily.	11 years ago
renat-sabitov-sirca	d046e1cc5b	Fixing transient AWS errors during EBS builds ... Relates to #1539 AWS is eventually consistent and instance can be not visibile for some time after creation. This fix eliminates describe-instances call before going to the proper wait loop	11 years ago
Mitchell Hashimoto	e422a45449	fmt	11 years ago
Josh Graham	5a2c4fe8a0	builder/amazon: Extend timeout and allow user override [GH-1533] ... - help resolve https://github.com/mitchellh/packer/issues/1533 (although timeouts are always ultimately useless in a distributed system!) - makes packer no more idempotent or janitorial than before - derive maximum number of ticks from timeout - default timeout to 300s (5m) to cater for global AMI copying - allow user to override with AWS_TIMEOUT_SECONDS environment variable	11 years ago
Mitchell Hashimoto	010cdb2057	amazon/common: style	12 years ago
Matt Page	6fb2586fb2	fix: Ignore transient network errors when fetching AWS state. ... Given that state fetching is an idempotent operation, a transient network error should not cause the entire build to fail. Instead, retry when such errors are encountered.	12 years ago
Henry Huang	5d410bddc9	When unexpected state found in waiting, notify the caller func with a correct error message	12 years ago
Henry Huang	c33e7cc867	Add the support of launching spot instances in "amazon-ebs" AMI	12 years ago
Mitchell Hashimoto	1234e61cda	builder/amazon/all: get rid of unnecessary field	12 years ago
Patrick Lucas	e17984face	Fix race condition after launching EC2 instance ... It is possible for an instance to not immediately exist after it is launched. Previously, InstanceStateRefreshFunc would crash if this race condition were realized. This change takes the exact same approach of the function above, AMIStateRefreshFunc, treating 'InvalidInstanceID.NotFound' as if there were an empty result.	13 years ago
Mitchell Hashimoto	61320b20a9	builder/amazon/common: error if WaitForState can't find resource ... repeatably	13 years ago
Mitchell Hashimoto	1bf91e2845	builder/amazon/common: rename instance.go to state.go, makes more sense	13 years ago