Skip to content

Deployment at Groundwire

Jump to bottom
Kenan Scott edited this page Dec 18, 2017 · 3 revisions

  • Builds and deployments are automated by CodePipeline. Changes to the prod branch will run the fetch the sources, run the build and deploy to the dev CloudFormation stack automatically. Approve in order to deploy to prod.

  • Changes to responses templates should be done manually using awscli, see Creating and updating email tempaltes.

  • Two configuration files are used, template-map.json, which is documented in the README and config.zip.

config.zip is designed to be an input artifact into CodePipeline and contains all the necessary parameters for CloudFormation in a single file, config.json, looking like

{
  "Parameters" : {
    "GoogleClientEmail": "",
    "GooglePrivateKeyEncrypted": "",
    "GoogleSpreadsheetId": "",
    "KmsKeyArn": "",
    "ForwardAddress": "",
    "EmailBucket": "",
    "ForwardFromName": "",
    "ForwardFromAddress": ""
  }
}

All the parameters are documented in the wiki.

Zip the config.json only and CodePipeline should be able to ingest the file properly. Upload both files to S3. Set the S3 URI for config.zip in the S3 source step of CodePipeline. Set the S3 URI for template-map.json as environment variable MAP_LOCATION in the CodeBuild project.

Clone this wiki locally