Workflow failure: Update bridge, ecosystem providers #566
Assignees
Labels
kind/engineering
Work that is not visible to an external user
p1
A bug severe enough to be the next item assigned to an engineer
resolution/fixed
This issue was fixed
Milestone
Comments
pulumi-bot
added
kind/engineering
|
Driving by here @guineveresaenger since this is now on my critical path. Per our convo I'll check in on these:
|
|
gcp is done by hand pulumi/pulumi-gcp@58a53ad |
|
aws got done by Ian. |
import requests
plist = [
'akamai',
'archive',
'azuredevops',
'cloudflare',
'cloudinit',
'confluentcloud',
'datadog',
'dnsimple',
'ec',
'equinix',
'external',
'gitlab',
'hcloud',
'http',
'keycloak',
'kong',
'linode',
'local',
'null',
'oci',
'openstack',
'random',
'slack',
'tls',
'vault',
]
providers = [
'aiven',
'akamai',
'alicloud',
'archive',
'artifactory',
'auth0',
'azuredevops',
'civo',
'cloudamqp',
'cloudflare',
'cloudinit',
'confluentcloud',
'consul',
'databricks',
'datadog',
'digitalocean',
'dnsimple',
'docker',
'ec',
'equinix-metal',
'external',
'f5bigip',
'fastly',
'github',
'gitlab',
'hcloud',
'http',
'kafka',
'keycloak',
'kong',
'libvirt',
'linode',
'local',
'mailgun',
'minio',
'mongodbatlas',
'mysql',
'newrelic',
'nomad',
'ns1',
'null',
'oci',
'okta',
'onelogin',
'openstack',
'opsgenie',
'pagerduty',
'postgresql',
'rabbitmq',
'rancher2',
'random',
'rke',
'signalfx',
'slack',
'snowflake',
'splunk',
'spotinst',
'sumologic',
'tailscale',
'tls',
'vault',
'venafi',
'vsphere',
'wavefront',
]
for provider in providers:
resp = requests.get(f"https://raw.githubusercontent.com/pulumi/pulumi-{provider}/master/provider/go.mod")
for line in resp.text.split('\n'):
if 'github.com/pulumi/pulumi/pkg' in line:
if ('3.81.0' not in line) and ('3.82.1' not in line):
print("- [ ]", provider, line)
elif provider in plist:
print("- [x]", provider, line) |
|
Here's the current status summary: EXTEMPORAL UPDATE ON PROVIDER P1s:
|
|
I've updated the list. This is better. I'm going to take a stab at updating http and external after a bridge release that gets us past pulumi/pulumi-terraform-bridge#1379 |
|
Two left.. |
|
Also need to address #593. Going to look at a fix for that next |
guineveresaenger
added a commit
that referenced
this issue
Sep 21, 2023
Previous to this change, when the `upgrade-on-main` step failed, we would call `upgrade-on-master` every time, because the `if` condition on that step never made sense. But for providers where default branch is set to `main`, this would result in an overall failure, because `upgrade-on-master` does not specify `continue-on-error: true`. With this change, the `upgrade-on-master` step should no longer run at all for providers whose default branch is `main`. Note that using `github.event.repository.default_branch` is not available to us here, as that would detect the originating repo's (ci-mgmt's) default branch. Furthermore, this PR adds a Workflow to update a single ecosystem provider, so we can optionally do gradual/test rollouts of updates. Final note: There are a lot of "bridge updates" in this folder, and some are stale. To keep the scope tight, this is tracked in #579. Closes #566. Closes #593. - fix success logic on triggering against master ref - Add option to upgrade a single provider's bridge version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Workflow Failure
Update bridge, ecosystem providers has failed. See the list of failures below:
Ensure that every provider updated to p/p 3.81.0 and bridge 3.59.0.
Bridged Providers
Tier 1 - all upgraded
Tier 2 - not upgraded yet
Used a script to detect remaining here they are:
The text was updated successfully, but these errors were encountered: