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

Consolidate test workflow #1214

Merged
merged 2 commits into from
Dec 12, 2024
Merged

Consolidate test workflow #1214

merged 2 commits into from
Dec 12, 2024

Conversation

blampe
Copy link
Contributor

@blampe blampe commented Dec 11, 2024

  • Updates test-provider/aws/.ci-mgmt.yaml to what's currently checked-in.
  • Consolidates test jobs into a shared workflow using run-acceptance-tests as the starting point.

extraTests are included in the shared workflow mostly for simplicity. This will break aws because those tests will specify needs: that are no longer valid. We can fix that manually or just remove these extra tests (pulumi/pulumi-aws#4910, pulumi/pulumi-aws#4909).

No special treatment is given to TestPulumiExamples. We're not using this outside of azure-native, and it should really just be treated like any other integration test #1211. If we don't want these tests to run in certain workflows then we should expose some info to let them t.Skip themselves.

Fixes #1034

Copy link
Member

@danielrbradley danielrbradley left a comment

Choose a reason for hiding this comment

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

Very excited to see this go in!

I think it would be worth opening tentative PRs to a few key providers to get feedback before merging this. AWS, Azure and GCP at least. It would be good to prepare the fixes for AWS before merging too so that we're not scrambling to fix things after this merges.

@blampe
Copy link
Contributor Author

blampe commented Dec 12, 2024

Very excited to see this go in!

I think it would be worth opening tentative PRs to a few key providers to get feedback before merging this. AWS, Azure and GCP at least. It would be good to prepare the fixes for AWS before merging too so that we're not scrambling to fix things after this merges.

@danielrbradley AWS fixes are in :)

Test PRs

@blampe blampe added this pull request to the merge queue Dec 12, 2024
Merged via the queue into master with commit 3e4be1c Dec 12, 2024
6 checks passed
@blampe blampe deleted the blampe/test-consolidate branch December 12, 2024 23:01
github-merge-queue bot pushed a commit that referenced this pull request Dec 17, 2024
The `permissions` block in a reusable workflow doesn't grant these
permissions. These are more used as an early indication of the
permissions required by the reusable workflow. The correct permissions
still need to be set on the calling side.

See `Reusable workflows` in [this blog
article](https://www.kenmuse.com/blog/github-actions-workflow-permissions/).

Follow up to #1214.

Without setting the `permissions` on the calling side, the reusable
workflow will not have the correct permissions.

The Pulumiverse runs failed without the required `permissions` block:
https://github.com/pulumiverse/pulumi-acme/actions/runs/12365788538
After adding the `permissions` block on the calling side:
https://github.com/pulumiverse/pulumi-acme/actions/runs/12369028130

pulumiverse/pulumi-acme#98

For Pulumiverse, this fails because the organization wide workflow
settings are configured to `Read repository contents and packages
permissions`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Extract test shared workflow
2 participants