Alexharvey/1318 part 1

.circleci/README.md

@@ -2,14 +2,30 @@
 
 * `REPOSITORY_PATH` - directory in container where dest repo is initialized within container
 * `DEPLOYMENT_GIT_SSH` or `DEPLOYMENT_GIT_HTTPS`' - destination repository for rendered pages
-   * `DEPLOYMENT_GIT_SSH` - requires adding SSH key to the CircleCI + deploy key with push rights to the target repository 
+   * `DEPLOYMENT_GIT_SSH` - requires adding SSH key to the CircleCI + deploy key with push rights to the target repository
    * `DEPLOYMENT_GIT_HTTPS` - requires setting up personal access token with push rights to the target repository
 * `GITHUB_EMAIL` - email which is associated with commit message and github account
 * `GITHUB_TOKEN` - access token with push rights to the target repository `/docs`
 * `CIRCLE_USERNAME` - built in variable in CIRCLE CI - should be same as user who pushes to repository
+* `CI_SERVICE_AWS_ACCESS_KEY_ID` - The CI service user's AWS access key ID
+* `CI_SERVICE_AWS_SECRET_ACCESS_KEY` - The CI service user's AWS secret access key
 
 ##### Optional evn variables
 
 * `RENDERED_DOCS_DIR` - directory where rendered pages are stored within `DEST_REPO` - default is repository root
 * `DOCS_DEV_VERSION` - directory name where latest version of docs are published,
-   default value is `dev` will result in path `../docs/dev`
+   default value is `dev` will result in path `../docs/dev`
+
+
+
+##### Release Workflow
+
+This is the workflow used to publish Sceptre releases.
+
+* Verify that the latest CI build for Sceptre is green on the `master` branch
+* Checkout the latest master branch
+* Bump the Sceptre version (i.e. 2.4.0 -> 2.5.0) & update the CHANGELOG.md file
+* Commit and push the change
+* Create a tag (i.e. tag -a -s v2.6.0)
+* Push tag
+* The `publish` workflow is triggered on CI which will publish a new Sceptre release.

.circleci/add-known-hosts.sh

@@ -11,4 +11,4 @@ fi
 
 mkdir -p ~/.ssh
 
-ssh-keyscan -t rsa github.com >> ~/.ssh/known_hosts
+ssh-keyscan -t rsa github.com >> ~/.ssh/known_hosts