Skip to content

[Epic] Move provider sdk publishing into deployments #1607

Open
@mjeffryes

Description

@mjeffryes

Configuring a build environment for a provider is complicated because of the requirement to build and publish SDKs in each language. This creates obstacles for provider authors in our community who primarily use only 1 or 2 of the languages (and their distribution tools) Pulumi supports. It also complicates provider maintenance for Pulumi as we try to keep build systems running for 80+ providers.

Ideally, a provider author would like to be able to just build the provider binary, and then hand it off to a Pulumi managed publishing pipeline to build and publish the SDKs (and into their org private package registry too).

Fortunately, we already have a standard environment with all the Pulumi languages installed for Pulumi deployments. Constructing a Pulumi program that runs pulumi package gen-sdk for each language and publishes to the language registries would give provider authors a turn-key publishing solution

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageNeeds attention from the triage team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions