pulumi / upgrade-provider

A tool to automate provider upgrades on your local machine
6 stars 1 forks source link

Automate updating pinned external provider references #263

Open t0yv0 opened 5 months ago

t0yv0 commented 5 months ago

Hello!

Issue details

To stabilize provider builds we currently pin external provider references so that examples that use an external provider (i.e. aws provider when building a provider other than aws such as awsx) render in a stable manner. However issues remain when these references remain stale. Examples drop out or render inaccurately.

How are these pinned? See .ci-mgmt.yaml in pulumi-aws for a good recent example, it has a section:

plugins:
  - name: archive
    version: "0.0.1"
  - name: tls
    version: "4.10.0"
  - name: github
    version: "4.10.0"
  - name: kubernetes
    version: "4.11.0"
  - name: "null"
    version: "0.0.3"
  - name: "local"
    version: "0.1.0"
  - name: random
    version: "4.8.2"
  - name: github
    version: "5.14.0"
  - name: std
    version: "1.6.2"
  - name: terraform
    version: "1.0.17"
    kind: converter

Suggest automating this:

Affected area/feature

iwahbe commented 5 months ago

I think this is a great idea.

As part of doing this, we should move plugin versions to a separate lock file. I don't want upgrade-provider to be editing .ci-mgmt.yaml.