Label the repo on the Docker image

We've now labeled the Docker image with the repo URI.

Fail if a stackset instance fails to deploy

When rolling out a stackset we probably need to notify the caller if an instance fails to deploy.

s3:// URIs in template: parameter

Previously you could only upload and use local Cloudformation template files. This release will allow you to specify s3:// URIs in the template: property of the stack definition in the environment configuration, so the template files will be synced from a third-party S3-bucket.

Fix file access exception when no -m is specified

1.3.1 introduced a regression when cf-seed would bomb out if run without -m. This release fixes the bug.

Upload release manifest into S3 from local filesystem

In this release you can run cf-seed with a -m parameter pointed at a local file and it will automatically upload it to S3 and read back from there.

Mass includes and objectpath

This release adds two new tags into configuration:
!IncludeAll allows to mass-include files by wildcard and either merge or concatenate the result
!ObjectPath can run an objectpath expression over a data structure

These changes greatly support very large cf-seed deployments. Please see examples.

Support region_concurrency_type in operation_preferences for stacksets

Long-awaited region_concurrency_type

Allow CF templates without parameters

It was because of a simple mistake that templates without parameters weren't allowed. Let's correct it. Btw mandatory parameters are not that mandatory any more, but shhhh, don't tell anyone.

Add !EnvironmentVariable parameter tag

Now you can use !EnvironmentVariable to fill in your deployment parameters from the OS environment.

Organization-managed stacksets

This release allows you to deploy Cloudformation stacksets into Organizational Units using rollout_strategy: organization. Please see the readme.