feat | LAY-917 Added an action to create a new tag. Added scripts for…#30
Conversation
… release. Added guideline for release process
Lzok
force-pushed
the
feat/LAY-917-action-tag
branch
from
79aa5fa to
483ae09
Compare
There was a problem hiding this comment.
I setup the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in the production env and gave you permissions to add the other 3 we need (CLOUDFRONT_DISTRIBUTION_ID, CLOUDFRONT_DOMAIN, S3_BUCKET_NAME).
https://github.com/LayerLens/atlas-python/settings/environments/8110884380/edit
| jobs: | ||
| check-branch: | ||
| runs-on: ubuntu-latest | ||
| environment: development |
There was a problem hiding this comment.
This should run on the production env for the release branch (our production branch)
| on: | ||
| workflow_dispatch: | ||
| inputs: | ||
| dry_run: | ||
| description: "Run in dry-run mode (show what would be done without actually creating/pushing the tag)" | ||
| required: false | ||
| type: boolean | ||
| default: true | ||
| confirm_release: | ||
| description: "Type 'YES' to confirm you want to create and push the release tag" | ||
| required: true | ||
| type: string |
There was a problem hiding this comment.
We should configure the enviornment in this section so we don't specify it at each step.
The two env we have are development and production. The production env should be used on the release branch.
| create-release-tag: | ||
| runs-on: ubuntu-latest | ||
| needs: check-branch | ||
| environment: development |
There was a problem hiding this comment.
See comment above on not specifying the env on each step.
| jobs: | ||
| validate: | ||
| runs-on: ubuntu-latest | ||
| environment: development |
There was a problem hiding this comment.
We need this on the production env as well
2 participants
… release. Added guideline for release process