Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: multi regional deployment pipeline #218

Closed
wants to merge 2 commits into from
Closed

chore: multi regional deployment pipeline #218

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9bb9487
moved relayer-3 & relayer-4 to regions
eedygreen Sep 22, 2023
39c59ef
pipeline for regional deployments
eedygreen Sep 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/deploy_stage.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
relayer_id: [0, 1, 2, 3, 4]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not like that we are basically having copy of this file just to deploy to another region. Might we use if statements with matrix values? like if matrix.relayer_id.3 deploy to this region, etc.
Or for example we can use include statement of GA that allwos to add additional arguments to particular matrix elements. And we can use it to specify region per relayer_id

relayer_id: [0, 1, 2]

permissions:
contents: read
Expand Down
107 changes: 107 additions & 0 deletions .github/workflows/deploy_stage_regions.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,107 @@
# The Licensed Work is (c) 2022 Sygma
# SPDX-License-Identifier: LGPL-3.0-only

name: sygma_deploy_devnet_to_regions

on:
workflow_dispatch:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should not it be on push, the same it was before?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

workflow dispatch does not need push commit. If we are going to deploy manually, then the commit is not manual.

inputs:
region_2:
description: 'Regional deployment'
required: true
default: 'region'
type: string
region_3:
description: 'Regional deployment'
required: true
default: 'region'
type: string

env:
ENVIRONMENT: STAGE
AWS_STAGE: '${{ secrets.AWS_ARN }}'
REGISTRY: 'ghcr.io'
TAG: 'latest'

jobs:
deploy:
name: deploy
runs-on: ubuntu-latest
strategy:
matrix:
relayer_id_region_2: [3]
relayer_id_region_3: [4]

permissions:
contents: read
id-token: write

steps:
- name: checkout the source code
uses: actions/checkout@v3

- name: checkout ecs repo
uses: actions/checkout@v3
with:
repository: sygmaprotocol/devops
token: ${{ secrets.GHCR_TOKEN }}

- name: render jinja2 templates to task definition json files region 2
if: ${{ github.event.inputs.region_2 }} == ${{ github.secret.DEVNET_REGION_2}}
uses: cuchi/jinja2-action@v1.2.0
with:
template: 'relayers/ecs/task_definition-${{ env.ENVIRONMENT }}.j2'
output_file: 'relayers/ecs/task_definition-${{ matrix.relayer_id_region_2 }}_${{ env.ENVIRONMENT }}.json'
data_format: json
variables: |
relayerId=${{ matrix.relayer_id_region_2 }}
awsAccountId=${{ env.AWS_STAGE }}
awsRegion=${{ secrets.DEVNET_REGION_2 }}
awsEfs=${{ secrets.DEVNET_EFS_2 }}

- name: configure aws credentials
if: ${{ github.event.inputs.region_2 }} == ${{ github.secret.DEVNET_REGION_2}}
uses: aws-actions/configure-aws-credentials@v1
with:
role-to-assume: arn:aws:iam::${{ env.AWS_STAGE }}:role/github-actions-${{ env.ENVIRONMENT }}-chainbridge
aws-region: ${{ secrets.AWS_REGION_2 }}
role-session-name: GithubActions

- name: deploy task definition to region_2
if: ${{ github.event.inputs.region_2 }} == ${{ github.secret.DEVNET_REGION_2}}
uses: aws-actions/amazon-ecs-deploy-task-definition@v1
with:
task-definition: 'relayers/ecs/task_definition-${{ matrix.relayer_id_region_2 }}_${{ env.ENVIRONMENT }}.json'
service: 'relayer-${{ matrix.relayer_id_region_2 }}-service-${{ env.ENVIRONMENT }}'
cluster: 'relayer-${{ env.ENVIRONMENT }}'
wait-for-service-stability: true

- name: render jinja2 templates to task definition json files region 3
if: ${{ github.event.inputs.region_3 }} == ${{ github.secret.DEVNET_REGION_3}}
uses: cuchi/jinja2-action@v1.2.0
with:
template: 'relayers/ecs/task_definition-${{ env.ENVIRONMENT }}.j2'
output_file: 'relayers/ecs/task_definition-${{ matrix.relayer_id_region_3 }}_${{ env.ENVIRONMENT }}.json'
data_format: json
variables: |
relayerId=${{ matrix.relayer_id_region_3 }}
awsAccountId=${{ env.AWS_STAGE }}
awsRegion=${{ secrets.AWS_REGION_3 }}
awsEfs=${{ secrets.DEVNET_EFS_3 }}

- name: configure aws credentials
if: ${{ github.event.inputs.region_3 }} == ${{ github.secret.DEVNET_REGION_3}}
uses: aws-actions/configure-aws-credentials@v1
with:
role-to-assume: arn:aws:iam::${{ env.AWS_STAGE }}:role/github-actions-${{ env.ENVIRONMENT }}-chainbridge
aws-region: ${{ env.AWS_REGION_3 }}
role-session-name: GithubActions

- name: deploy task definition to region 3
if: ${{ github.event.inputs.region_3 }} == ${{ github.secret.DEVNET_REGION_3}}
uses: aws-actions/amazon-ecs-deploy-task-definition@v1
with:
task-definition: 'relayers/ecs/task_definition-${{ matrix.relayer_id_region_3 }}_${{ env.ENVIRONMENT }}.json'
service: 'relayer-${{ matrix.relayer_id_region_3 }}-service-${{ env.ENVIRONMENT }}'
cluster: 'relayer-${{ env.ENVIRONMENT }}'
wait-for-service-stability: true
Loading