-
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
Enable release verification in all providers #1201
Comments
I think we wanted to scope this down to tier 1. Adding to M115. |
Looks like these tests also run on main so they verify pre-releases across platforms and are a preventative as well as a discovery measure which is great. |
I cut this list down to just Tier 1 plus a few higher profile Tier 2 repos |
I'm working on random now. @mjeffryes If this is a P1, I think it should be assigned. Since it applies to all squads, I think that means you. |
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-random`.
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-tls`.
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-random`.
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-random`.
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-random`.
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-tls`.
As part of pulumi/ci-mgmt#1201, we are enabling release verification on `pulumi-random`.
pulumi/verify-provider-release#74 blocks release verification for random (and probably and tls and gcp) for python. pulumi/verify-provider-release#73 makes me hesitant to deploy release verification. I'm going to remove the python release verification on both random and tls until pulumi/verify-provider-release#74 is resolved. |
Example from azure:
Related to #967
Native Providers
Tier 1
Tier 2
Bridged Providers
Tier 1
Tier 2
The text was updated successfully, but these errors were encountered: