Qaz Beta!!!

This Qaz beta release sees the addition of a few features and enhancements.

Breaking change

• The source mechnism for specifying templates using -t --template flags has been enhanced. You will now need to specify the stack name when passing the template. This removes the need for the template to have the same name as the stack and allows for a multiple stacks to use the same source.

For Example:

$ qaz generate --template stack::path/to/template

$ qaz generate --template stack::http://some.endpoint

• file custom template function has been changed to cat

New Features

• Delimiter Selection for custom templates
• AWS Lambda can now be used as source for both config file and templates
• Cross-Account & Cross-Region mechanism enhanced to support multi region deployments
• Config files can now be written in JSON, great for fetching a config string via an API
• Templates can now be uploaded to S3 before deployment by specifying the bucket in config
• The QAZ_CONFIG environment variable can now be used when re-using the same config path or endpoint.

New Template Functions

• prefix function added
• suffix function added
• contains function added

Finally!

The Wiki is now starting to come together, more, tips, tricks and use cases to come!

Cross-Account Stack Deployments

• Qaz now supports cross-account deployments by utilising different profiles defined in AWS credentials configuration.

stacks:
  vpc:
    # specify profile based on aws credentials/config file
    profile: my_account_profile
    cf:
      cidr: 10.10.10.10/32

• Minor bug fixes and restructuring for upcoming beta.

Stack-Policy Functionality Now Supported

• Qaz now supports setting stack update policies using a new keyword in config: policy.

Example:

stacks:
  stackname:
    # stack policy - url or raw json can be specified here
    policy: https://s3-eu-west-1.amazonaws.com/daidokoro-dev/policies/stack.json

--

• set-policy Command added for updating stack policy based on config value.

$ qaz set-policy --help 

Set Stack Policies based on configured value

Usage:
  qaz set-policy [flags]

Examples:
qaz set-policy <stack name> -c <config.yml>

Flags:
  -c, --config string   path to config file (default "config.yml")

Global Flags:
      --debug            Run in debug mode...
  -p, --profile string   configured aws profile (default "default")

--

• tail Command removed.
• New Config Reader backend provides better exception handling and stability.

RollBack!

• Deploy command now supports setting stack rollback on failure.

$ qaz deploy -c config.yml -t template.yml --rollback

• Qaz commands code restructured
• Minor bug fixes

Minor Bug Fixes

• Bug Fixes and code enrichment

Lambda Fix

• Fixed Lambda bug from Previous Release
• Added Exception Handler for bad Lambda Functions

Encrytion & Decryption now Supported via KMS

• New KMS Encryption/Decryption Gen/Deploy Time functions. Qaz can now encrypt values within a template or decrypt and deploy encrypted template ciphers.

• Minor bug fixes.

• Enhanced error reporting for Gen/Deploy Time functions

Bug Fixes

• Added IAM Capabilities to Change-Set Create command
• Fixed Deploy issue cause by missing IAM Capabilities
• Removed Cost Estimate, feature will not be supported going forward
• Minor code tweaks and optimisation

Change-Set Management Added

• Change-Set Management Now Support.
• Minor improvements and bug fixes in the back-end.

Emergency Bug-Fix for Deploy-Time Function

• Resolved issue with Deploy-Time functions not being triggered.