You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -482,3 +482,38 @@ This returns your token, which you can use in testing the authentication on the
482
482
483
483
The /api/v1/verify route get's the client keys and redirect uri from the bucket.
484
484
485
+
### Deployments with Concourse
486
+
487
+
#### Allowlisting your IP
488
+
To setup the deployment pipeline with concourse, you must first allowlist your IP address on the Concourse
489
+
server. IP addresses are flushed everyday at 00:00 so this must be done at the beginning of every working day
490
+
whenever the deployment pipeline needs to be used. Follow the instructions on the Confluence page (SDP Homepage > SDP Concourse > Concourse Login) to
491
+
login. All our pipelines run on sdp-pipeline-prod, whereas sdp-pipeline-dev is the account used for
492
+
changes to Concourse instance itself. Make sure to export all necessary environment variables from sdp-pipeline-prod (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN).
493
+
494
+
#### Setting up a pipeline
495
+
When setting up our pipelines, we use ecs-infra-user on sdp-dev to be able to interact with our infrastructure on AWS. The credentials for this are stored on
496
+
AWS Secrets Manager so you do not need to set up anything yourself.
497
+
498
+
To set the pipeline, run the following script:
499
+
```bash
500
+
chmod u+x ./concourse/scripts/set_pipeline.sh
501
+
./concourse/scripts/set_pipeline.sh KEH-TAT-API
502
+
```
503
+
Note that you only have to run chmod the first time running the script in order to give permissions.
504
+
This script will set the branch and pipeline name to whatever branch you are currently on. It will also set the image tag on ECR to the current commit hash at the time of setting the pipeline.
505
+
506
+
The pipeline name itself will usually follow a pattern as follows: `<repo-name>-<branch-name>`
507
+
If you wish to set a pipeline for another branch without checking out, you can run the following:
If the branch you are deploying is "main" or "master", it will trigger a deployment to the sdp-prod environment. To set the ECR image tag, you must draft a Github release pointing to the latest release of the main/master branch that has a tag in the form of vX.Y.Z. Drafting up a release will automatically deploy the latest version of the main/master branch with the associated release tag, but you can also manually trigger a build through the Concourse UI or the terminal prompt.
513
+
514
+
#### Triggering a pipeline
515
+
Once the pipeline has been set, you can manually trigger a build on the Concourse UI, or run the following command:
0 commit comments