Skip to content
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.

fix: Monitoring Lambda functions (#63) #76

fix: Monitoring Lambda functions (#63)

fix: Monitoring Lambda functions (#63) #76

Workflow file for this run

---
name: Deploy
on:
push:
branches:
- master
permissions:
id-token: write
contents: read
defaults:
run:
shell: bash
jobs:
deploy:
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: '3.8'
- uses: aws-actions/configure-aws-credentials@v1-node16
with:
role-to-assume: arn:aws:iam::853553028582:role/github-openid-connect
role-session-name: github-actions-monitoring-jump-start
aws-region: eu-west-1
- run: |
aws s3 sync . s3://monitoring-jump-start --exclude '*' --include 'marbot*.yml' --include 'data/*' --delete
for file in marbot*.yml; do version=$(yq e '.Outputs.StackVersion.Value' $file); if [ "$version" != "null" ]; then aws s3 cp $file s3://monitoring-jump-start/v$version/$file; fi; done