Deploying from the command line

Usage: stackery deploy <stack> <env> <ref>

Required Parameters

  1. stack The name of the stack you want to deploy.
  2. env The name of the Environment you want the stack to deploy to.
  3. ref A branch name, tag, or commit SHA, etc. Note: Deployments are generated from the stack’s remote git repository. Be sure to push any local changes to the remote repository before deploying!

Optional Flags

  • --aws-profile <profileName> Specify the AWS profile to use from your AWS Credentials File. If not provided, you will be prompted to provide your profile or credentials.
  • --access-key-id <awsAccessKeyID> Provide your AWS Access Key ID directly via the command line rather than using an AWS profile. If set, --secret-access-key must also be provided
  • --secret-access-key <awsSecretAccessKey> Provide your AWS Secret Access KEy directly via the command line rather than using an AWS profile. If set, --access-key-id must also be provided

AWS Credentials

There are a number of ways to provide your AWS credentials to Stackery. In order of priority:

  1. The --aws-profile <profileName> flag. No further input will be required from you. We recommend you use this method when running the cli non-interactively.
  2. If the environment variables AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION are set, you will be asked if you want to use them.
  3. If you have an AWS Credentials File, you will be asked if you want to use one of them
  4. Otherwise you will be prompted to enter the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY values you want to use.

Examples

$ stackery deploy redPenguin staging development --aws-profile groot

This command will deploy the development branch of stack redPenguin to your staging environment, using the aws-profile groot

Try Stackery For Free

Gain control and visibility of your serverless operations from architecture design to application deployment and infrastructure monitoring.