Back to Reference Index

cody start

Usage

cody start

Description

start codebuild project.

Examples

cody start # infers the name from the parent folder
cody start stack-name # looks up project via CloudFormation stack
cody start demo-project # looks up project via codebuild project name

Overriding Env Variables at Runtime

You can override env variables at runtime with --env-vars. Examples:

cody start --type vpc --env-vars K1=v1 K2=v2
cody start --type vpc --env-vars K1=v1 K2=ssm:v2 # support for PARAMETER_STORE

Options

    [--source-version=SOURCE_VERSION]  # git branch
                                       # Default: master
b, [--branch=BRANCH]                   # git branch
                                       # Default: master
    [--env-vars=one two three]         # env var overrides. IE: KEY1=VALUE1 KEY2=VALUE2
t, [--type=TYPE]                       # folder to use within .cody folder for different build types
    [--stack-name=STACK_NAME]          # Override the generated stack name. If you use this you must always specify it
    [--wait], [--no-wait]              # Wait for operation to complete
                                       # Default: true
    [--verbose], [--no-verbose]        
    [--noop], [--no-noop]

Edit this page

See a typo or an error? You can improve this page. This website is available on GitHub, and contributions are encouraged and welcomed. We love pull requests from you!