Use Terminus CLU (#203)

* Use Terminus CLU for CircleCI
* Use Terminus CLU for GitLab
* Exit on errors for BitBucket CLU job

Author: ataylorme

.circleci/config.yml

@@ -217,9 +217,13 @@ jobs:
           name: setup-environment-vars
           command: /build-tools-ci/scripts/set-environment
 
+      - run:
+          name: Authenticate with Terminus
+          command: terminus -n auth:login --machine-token="$TERMINUS_TOKEN"
+
       - run:
           name: run composer lock updater
-          command: set -e && clu https://${GITHUB_TOKEN}:[email protected]/${CI_PROJECT_USERNAME}/${CI_PROJECT_REPONAME}.git | sed -e "s/${GITHUB_TOKEN}/[REDACTED]/g"
+          command: set -e && terminus project:clu $TERMINUS_SITE
 
 workflows:
   version: 2

.gitlab-ci.yml

@@ -155,19 +155,7 @@ test:behat:cleanup:
 
 schedule:composer:update:
   stage: updates
-  variables:
-    # The default set of CI credentials do not contain the necessary permissions in GitLab for our operations.
-    LAB_CORE_TOKEN: $GITLAB_TOKEN
-    LAB_CORE_USER: $CI_REGISTRY_USER
-    LAB_CORE_HOST: "https://$CI_SERVER_HOST"
-    GIT_STRATEGY: none
   script:
-  # The default repository URL uses a token without permission to write so replace it with ours.
-  - FULL_REPOSITORY_URL=$(sed 's|'"$CI_JOB_TOKEN"'|'"$GITLAB_TOKEN"'|' <<< "$CI_REPOSITORY_URL")
-  # lab tries to use CI variables with improper permissions.
-  - unset CI_PROJECT_URL
-  - unset CI_REGISTRY_USER
-  - unset CI_JOB_TOKEN
-  - set -e && clu --provider=gitlab $FULL_REPOSITORY_URL
+  - set -e && terminus project:clu $TERMINUS_SITE
   only:
   - schedules

bitbucket-pipelines.yml

@@ -127,4 +127,4 @@ pipelines:
           - export CI_PROJECT_NAME=$BITBUCKET_REPO_FULL_NAME && echo $CI_PROJECT_NAME
           - /build-tools-ci/scripts/set-environment
           - terminus -n auth:login --machine-token="$TERMINUS_TOKEN"
-          - terminus project:clu $TERMINUS_SITE
+          - set -e && terminus project:clu $TERMINUS_SITE