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.

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

OPS-5160 Trigger infra-dev rollout on push to main #9

Closed
Closed
Changes from all commits
Commits
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
19 changes: 19 additions & 0 deletions .github/workflows/trigger-awx-on-push-to-master.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
name: Trigger AWX on push to master

on:
push:
branches:
- main
paths:
- modules/**

permissions: {}

jobs:
trigger_awx:
uses: hpi-schul-cloud/infra-tools/.github/workflows/trigger-awx.yaml@master
with:
job_id: 33
secrets:
AWX_TOKEN: ${{ secrets.AWX_TOKEN }}
Copy link
Contributor

Choose a reason for hiding this comment

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

is this necessary? The version of the terraform modules is set in infra-schulcloud as variable in the new approach, so this execution would not test anything new would it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good point, but maybe we should always use the latest version on infra-dev to catch issues early. Otherwise we would need to think of a way to have different versions of the Terraform modules on infra-dev and on the other stages.

Loading