-
Notifications
You must be signed in to change notification settings - Fork 4
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
Generate workflows for aws #518
Conversation
47a0565
to
baa0f50
Compare
8786cf6
to
8ec6279
Compare
We missed updating this when we removed `.Config.actionVersions.setupGo` to `.Config.actions.setupGo`. These workflows were broken, and this fixes them.
8ec6279
to
a9bb324
Compare
a9bb324
to
0e7a98d
Compare
This relies on pulumi/ci-mgmt@fa795bc and pulumi/ci-mgmt@727247e from pulumi/ci-mgmt#518.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great at first glance.
Can you add an explanation why we need the extraTests
config option? I'm assuming it's because we want to test the provider shim in AWS but nowhere else - however I don't see an extra shim test action being generated; what am I missing?
go_test_shim: | ||
if: github.event_name == 'repository_dispatch' || github.event.pull_request.head.repo.full_name == github.repository | ||
name: Run test of provider shim | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout Repo | ||
uses: actions/checkout@v3 | ||
with: | ||
ref: ${{ env.PR_COMMIT_SHA }} | ||
submodules: true | ||
- uses: actions/setup-go@v4 | ||
with: | ||
cache-dependency-path: provider/shim/go.sum | ||
go-version-file: provider/shim/go.mod | ||
- name: go test | ||
run: | | ||
cd provider/shim | ||
go test -v . | ||
timeout-minutes: 60 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great at first glance.
Can you add an explanation why we need the
extraTests
config option? I'm assuming it's because we want to test the provider shim in AWS but nowhere else - however I don't see an extra shim test action being generated; what am I missing?
You're right, we use extraTests
for testing the shim. Each item in extraTests
is instantiated wherever we do tests (run-acceptance-tests.yml
, master.yml
, main.yml
, prerelease.yml
and release.yml
), and then back-linked as a needs
dependency wherever other tests are linked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
…2708) This PR is based off of pulumi/ci-mgmt#518. The Makefile has greater changes, which will be handled in a separate PR. There are outstanding changes in these files: - [ ] Makefile - [x] .github/workflows/main.yml - [x] .github/workflows/master.yml - [x] .github/workflows/nightly-test.yml - [x] .github/workflows/prerelease.yml - [x] .github/workflows/release.yml - [x] .github/workflows/run-acceptance-tests.yml - [x] .github/workflows/update-bridge.yml - [X] .github/workflows/command-dispatch.yml - [X] .github/workflows/community-moderation.yml - [X] .github/workflows/pull-request.yml - [X] .github/workflows/resync-build.yml - [X] .github/workflows/upgrade-bridge.yml - [X] .github/workflows/upgrade-provider.yml - [X] .goreleaser.prerelease.yml - [X] .goreleaser.yml - [X] .upgrade-config.yml - [X] scripts/upstream.sh We will merge as soon as we release v6. I expect the Makefile normalization to occur later.
This PR generated the workflow files for pulumi/pulumi-aws#2708.
This does not account for aws's Makefile, which is still non-standard. To make this safe to merge, we skip generating a Makefile for pulumi-aws (leaving the current one in place).
Improvements to ci-mgmt:
We are waiting to merge until aws v6 has launched.v6 has launched and we have updated pulumi-aws's workflows. Merging now.