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

Check why several providers did not auto-upgrade to the latest bridge version #1474

Closed
t0yv0 opened this issue Oct 25, 2023 · 0 comments · Fixed by #1471
Closed

Check why several providers did not auto-upgrade to the latest bridge version #1474

t0yv0 opened this issue Oct 25, 2023 · 0 comments · Fixed by #1471
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@t0yv0
Copy link
Member

t0yv0 commented Oct 25, 2023

What happened?

Using this monitoring script:

#!/usr/bin/env bash

set -euo pipefail


providers=$(curl https://raw.githubusercontent.com/pulumi/ci-mgmt/master/provider-ci/providers.json | jq -r .[])

echo "| P | br | pf | pkg | sdk |"
for p in $providers
do
    D="/tmp/pulumi-$p"
    if test -d "$D"; then
        (cd "$D" && git pull --quiet >/dev/null)
    else
        (cd /tmp && git clone --quiet --depth=1 "[email protected]:pulumi/pulumi-$p.git") >/dev/null
    fi

    V1=$(cd "$D/provider" && go list -f '{{.Version}}' -m github.com/pulumi/pulumi-terraform-bridge/v3)
    V2=$(cd "$D/provider" && (go list -f '{{.Version}}' -m github.com/pulumi/pulumi-terraform-bridge/pf 2>/dev/null || echo "NA"))
    V3=$(cd "$D/provider" && go list -f '{{.Version}}' -m github.com/pulumi/pulumi/pkg/v3)
    V4=$(cd "$D/provider" && go list -f '{{.Version}}' -m github.com/pulumi/pulumi/sdk/v3)
    echo "| pulumi-$p | $V1 | $V2 | $V3 | $V4 |"
done

It seems that several providers didn't upgrade to latest:

| P                     | br      | pf      | pkg     | sdk     |
|-----------------------+---------+---------+---------+---------|
| pulumi-archive        | v3.61.0 | v0.17.0 | v3.86.0 | v3.86.0 |
| pulumi-artifactory    | v3.62.0 | v0.18.1 | v3.89.0 | v3.89.0 |
| pulumi-confluentcloud | v3.60.1 | NA      | v3.81.0 | v3.81.0 |
| pulumi-databricks     | v3.62.0 | NA      | v3.89.0 | v3.89.0 |
| pulumi-ec             | v3.60.1 | v0.16.1 | v3.81.0 | v3.81.0 |
| pulumi-external       | v3.60.1 | v0.16.1 | v3.84.0 | v3.84.0 |
| pulumi-http           | v3.61.0 | v0.17.0 | v3.86.0 | v3.86.0 |
| pulumi-libvirt        | v3.61.0 | NA      | v3.86.0 | v3.86.0 |
| pulumi-local          | v3.61.0 | v0.17.0 | v3.86.0 | v3.86.0 |
| pulumi-minio          | v3.62.0 | NA      | v3.89.0 | v3.89.0 |
| pulumi-nomad          | v3.61.0 | NA      | v3.86.0 | v3.86.0 |
| pulumi-null           | v3.61.0 | v0.17.0 | v3.86.0 | v3.86.0 |
| pulumi-onelogin       | v3.61.0 | NA      | v3.86.0 | v3.86.0 |
| pulumi-opsgenie       | v3.62.0 | NA      | v3.89.0 | v3.89.0 |
| pulumi-rke            | v3.61.0 | NA      | v3.86.0 | v3.86.0 |
| pulumi-slack          | v3.61.0 | NA      | v3.86.0 | v3.86.0 |
| pulumi-snowflake      | v3.62.0 | NA      | v3.89.0 | v3.89.0 |
| pulumi-sumologic      | v3.61.0 | NA      | v3.86.0 | v3.86.0 |
| pulumi-tailscale      | v3.61.0 | NA      | v3.86.0 | v3.86.0 |

Would be good to understand why.

Example

N/A

Output of pulumi about

N/A

Additional context

N/A

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@t0yv0 t0yv0 added needs-triage Needs attention from the triage team kind/bug Some behavior is incorrect or out of spec labels Oct 25, 2023
t0yv0 added a commit that referenced this issue Oct 26, 2023
Editing the GitHub actions workflow to propagate new bridge releases to
all providers.

Fixes #1470
Fixes #1474
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Oct 26, 2023
@t0yv0 t0yv0 removed the needs-triage Needs attention from the triage team label Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants