Skip to content

Commit

Permalink
Remove paas Github environments
Browse files Browse the repository at this point in the history
They were still referenced in some places. The new environments are only
the *_aks ones.
  • Loading branch information
saliceti committed Jan 18, 2024
1 parent c801af5 commit 9af8432
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/manual.yml
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ jobs:
azure-credentials: ${{ secrets.AZURE_CREDENTIALS }}

- name: Slack Release Notification
if: steps.tag_id.outputs.release_id && github.event.inputs.environment == 'Production'
if: steps.tag_id.outputs.release_id && github.event.inputs.environment == 'production_aks'
uses: rtCamp/action-slack-notify@master
env:
SLACK_COLOR: ${{env.SLACK_SUCCESS}}
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/trello.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ jobs:
name: Link Trello card to this PR
if: "!contains( 'dependabot[bot] snyk-bot' , github.actor )"
runs-on: ubuntu-latest
environment: Development
environment: development_aks
steps:
- uses: Azure/login@v1
with:
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ The API is deployed to [AKS](https://github.com/DFE-Digital/teacher-services-clo

### Process

When you merge a branch to `master` it will automatically be deployed to the [development](#environments) and [test](#environments) environments via GitHub Actions and a tagged release will be created (the tag will use the PR number). You can then test the changes using the corresponding dev/test environments of the other GiT services. Once you're happy and want to ship to [production](#environments) you need to note the tag of your release and go to the `Manual Release` GitHub Action; from there you can select `Run workflow`, choose the `Production` environment and enter your release number.
When you merge a branch to `master` it will automatically be deployed to the [development](#environments) and [test](#environments) environments via GitHub Actions and a tagged release will be created (the tag will use the PR number). You can then test the changes using the corresponding dev/test environments of the other GiT services. Once you're happy and want to ship to [production](#environments) you need to note the tag of your release and go to the `Manual Release` GitHub Action; from there you can select `Run workflow`, choose the `production_aks` environment and enter your release number.

### Rollbacks

Expand Down

0 comments on commit 9af8432

Please sign in to comment.