-
Notifications
You must be signed in to change notification settings - Fork 5
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
Conversation
94f51fa
to
ef98e62
Compare
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.
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
|
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`.
test-provider/aws/.ci-mgmt.yaml
to what's currently checked-in.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 specifyneeds:
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