This repository contains shell scripts that assist in the process of building Sentera's various services that run on AWS.

env-tags.sh

This shell script is used when building a Docker image to determine the environments for which the image should be tagged, based upon the branch being built.

The branch name -> environment name mapping is:

• dev or dev.* branch -> dev environment
• staging or staging.* branch -> staging environment
• staging2 or staging2.* branch -> staging2 environment
• main or master branch -> prod environment

Example usage

This is a handy one-liner that can be used in a build script:

env_tags=$(wget -O - https://github.com/SenteraLLC/build-support/raw/master/env-tags.sh | bash)

push-to-ecr.sh

This shell script pushes a built Docker image and tags that reference this image to AWS ECR.

For example, when building on the main or master branch, the resulting tags pushed to ECR would look like the following: 2021-09-09.2a638c4, prod.

Example usage

This is a handy one-liner that can be used in a build script:

wget -O - https://github.com/SenteraLLC/version.sh/raw/master/push-to-ecr.sh | bash

version.sh

This shell script will inspect your project to determine a version number when deploying your service, and return a version number to stdout.

Three supported scenarios

As described below, version.sh output is contingent on:

• git branch of the project (master vs. non-master)
• presence of a .version file

.version file on master branch

If you track versions manually, either using SemVer or some other scheme, you can put it into a .version file in the root directory of your project. The contents of the .version file are returned with a v prefix. For example... contents of version file:

1.0.0

version.sh output:

v1.0.0

Note: You could auto-generate a .version file automatically (eg. via Travis-CI) based on that same information tracked elsewhere, such as package.json.

YYYY-MM-DD.SHA on master branch

If you do not track versions manually (i.e. a .version file does not exist in your project), a version will be created using the current date followed by the git SHA of the HEAD, e.g. 2019-10-2.b3bf3d9

branch/sha on non-master branch

If you are not on master, the version will indicate the deployed branch followed by the SHA of that branch, e.g. a-test-branch/53574e8, irrespective of whether you have a tracked version for master.

Example usage

This is a handy one-liner that can be used in a build script:

wget -O - https://github.com/SenteraLLC/build-support/raw/master/version.sh | bash