tpd-pete 0.5.0

TPD Pete is a AWS Deployment tool for AWS Cloudformation

TPD Pete

TPD Pete is an AWS Deployment tool for AWS Cloudformation

Configure

To setup pete use: pete configure to setup the default profile and region for AWS

Usage

To use pete for a project, first set it up using: pete init. This will generate the nessacary files for pete to function.

Then simply use: pete deploy to let deploy to your deployment AWS profile. If you want to deploy to your production environment use: pete deploy --production

If you have multiple collaborators on a project, and you dont want to share the same development environment. Then you could also use pete init --local to setup some development override for you locally. These will be used instead of the project development environment setup, if this has been setup.

So if you dont have local overrides, it uses the project config. If you dont have a project config, it uses the global config which is specific to you. You can save which account, region or bucket to use for a project in the project config. This will be saved in the .pete folder in you project folder. You should add this file to your VCS (like Git or SVN). But not the local file inside that folder, which hold the local overrides.

CI

For CI usage.

1. First set the PETE_CI variable to 1

2. Fill the following variables with the global configuration values | Key | Description | | PETE_DEV_PROFILE | AWS profile for Development | | PETE_PROD_PROFILE | AWS profile for Production | | PETE_DEV_BUCKET | S3 upload bucket for Development code | | PETE_PROD_BUCKET | S3 upload bucket for Production code | | PETE_DEV_REGION | Region to deploy to for Development | | PETE_PROD_REGION | Region to deploy to for Production |

3. You can also use the environment keys for AWS access key to override any profile settings. For more information see: Boto docs | Key | Description | | AWS_ACCESS_KEY_ID | Accesskey for AWS Cli | | AWS_SECRET_ACCESS_KEY | Secretkey for AWS Cli |