... used to build role AMIs for the bookings product
Each subdir is a role definition containing a Makefile, and any bespoke uploads or build scripts for that role. Building a role generates an AWS AMI.
Enter the role directory corresponding to the AMI you wish to build.
Clone packer_includes at level of Makefile. Checkout a tag if desired. (The x.y.z tags should represent a stable version of packer_includes).
If you do use a tag, add the line:
export PACKER_INCLUDES_GIT_TAG=... # replace dots with the tag value.
This will let you know in the future which dependency to use to reproduce this build.
Export vars deliberately not defined in Makefile.
Check all of the sources defined in the Makefile including git tags etc ... exist.
Amend the Makefile as required.
make clean build
If you are playing around with the puppet stuff that appears under uploads/puppet, on subsequent avoid the clean target.
make build # don't trash my modifications under puppet dir
-
The puppet stuff depends on a bunch of 3rd party modules.
These may cease to exist at a future date.
-
When building an appsvr (EUROSTAR_SERVICE_ROLE), you need to
specify an APP_VERSION that actually exists in AWS dev s3 under:
/enovation/$EUROSTAR_SERVICE_NAME/artefacts/integration/$APP_VERSION
TODO: stop using env specific folders for versioned artefacts!
-
Make error: *** You must pass env var AMI_PREVIOUS_SOURCES to make. Stop.
Usually this indicates that a suitable source ami can't be found.
Are you specifying a channel in your Makefile? e.g. stable or *