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

Updating link to correct manual jobs #497

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Updating link to correct manual jobs #497

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 source/cloud-native-platform/environments/auto-shutdown.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ See below the list of environments that are shut down outside of working hours o
Currently we start and stop the AKS Clusters, Application Gateways and Postgres Flexible Servers for the abovementioned environments. If required, the resources in an environment can be started outside of these hours using a GitHub action on the [auto-shutdown](https://github.com/hmcts/auto-shutdown) repository.

#### Start a specific environment
1. Navigate to [Manual Start](https://github.com/hmcts/auto-shutdown/actions/workflows/manual-start.yaml) action on the auto-shutdown repository.
1. Navigate to [Manual Start](https://github.com/hmcts/auto-shutdown/actions/workflows/manual-start-stop.yaml) action on the auto-shutdown repository.
2. Select 'Run Workflow'
3. Ensure the 'master' branch and the correct Business Area, Environment and Cluster option are selected. Then select 'Run Workflow'
4. Select the new build which will appear at the top under Workflow Runs and will be identifiable by an orange dot which means the build is currently running.
Expand Down
Loading