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

Enable release verification in all providers #1201

Open
3 of 12 tasks
danielrbradley opened this issue Dec 5, 2024 · 5 comments
Open
3 of 12 tasks

Enable release verification in all providers #1201

danielrbradley opened this issue Dec 5, 2024 · 5 comments
Assignees
Labels
kind/task Work that's part of an ongoing epic p1 A bug severe enough to be the next item assigned to an engineer

Comments

@danielrbradley
Copy link
Member

danielrbradley commented Dec 5, 2024

Example from azure:

releaseVerification:
  nodejs: examples/topic
  python: examples/eventhub-py
  dotnet: examples/appservice-cs
  go: examples/network-go

Related to #967

Native Providers

Tier 1

Tier 2

Bridged Providers

Tier 1

Tier 2

@pulumi-bot pulumi-bot added the needs-triage Needs attention from the triage team label Dec 5, 2024
@t0yv0
Copy link
Member

t0yv0 commented Dec 5, 2024

I think we wanted to scope this down to tier 1. Adding to M115.

@t0yv0
Copy link
Member

t0yv0 commented Dec 5, 2024

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.

@mjeffryes mjeffryes added p1 A bug severe enough to be the next item assigned to an engineer kind/task Work that's part of an ongoing epic and removed needs-triage Needs attention from the triage team labels Dec 5, 2024
@mjeffryes
Copy link
Member

I cut this list down to just Tier 1 plus a few higher profile Tier 2 repos

@iwahbe
Copy link
Member

iwahbe commented Dec 10, 2024

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.

iwahbe added a commit to pulumi/pulumi-random that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are enabling release
verification on `pulumi-random`.
iwahbe added a commit to pulumi/pulumi-tls that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are enabling release
verification on `pulumi-tls`.
iwahbe added a commit to pulumi/pulumi-random that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are enabling release
verification on `pulumi-random`.
iwahbe added a commit to pulumi/pulumi-random that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are enabling release
verification on `pulumi-random`.
iwahbe added a commit to pulumi/pulumi-random that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are enabling release
verification on `pulumi-random`.
iwahbe added a commit to pulumi/pulumi-tls that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are
enabling release verification on `pulumi-tls`.
iwahbe added a commit to pulumi/pulumi-random that referenced this issue Dec 10, 2024
As part of pulumi/ci-mgmt#1201, we are
enabling release verification on `pulumi-random`.
@iwahbe
Copy link
Member

iwahbe commented Dec 11, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Work that's part of an ongoing epic p1 A bug severe enough to be the next item assigned to an engineer
Projects
None yet
Development

No branches or pull requests

5 participants