Skip to content

community-packages: add DefangLabs/pulumi-defang (defang-aws, defang-gcp, defang-azure)#11109

Open
lionello wants to merge 1 commit into
pulumi:masterfrom
DefangLabs:community-packages/defang-multi-cloud
Open

community-packages: add DefangLabs/pulumi-defang (defang-aws, defang-gcp, defang-azure)#11109
lionello wants to merge 1 commit into
pulumi:masterfrom
DefangLabs:community-packages/defang-multi-cloud

Conversation

@lionello
Copy link
Copy Markdown

@lionello lionello commented May 21, 2026

Summary

Adds three new community packages for the Defang Pulumi provider — one per target cloud — at v2.1.1:

  • defang-aws — Deploy containerized services to AWS
  • defang-gcp — Deploy containerized services to GCP
  • defang-azure — Deploy containerized services to Azure

All three share the single-source repo DefangLabs/pulumi-defang and the same docs/_index.md + docs/installation-configuration.md (the docs cover all three clouds in one page for now; we'll split per-package in a follow-up if useful).

The previous single-schema entry (defang) is now obsolete — the provider has been split into three cloud-specific schemas. This PR also marks it publisher: DEPRECATED so the publishing scripts skip it, and removes its cached content (replaced by the three new packages).

This PR fixes the issues raised by @borisschlosser in #10890

Checklist

  • Released v2.1.1 (valid semver).
  • SDKs published in TypeScript (npm), Python (PyPI), Go (via repo tag), and .NET (NuGet) — for all three clouds. Java not published.
  • Three schema.json files checked in at the paths referenced by community-packages/package-list.json.
  • docs/_index.md and docs/installation-configuration.md present in the source repo; the install doc links to all published SDKs.

🤖 Generated with Claude Code

…gcp, defang-azure)

Add three new community packages for the Defang Pulumi provider — one per
target cloud (AWS, GCP, Azure) — at v2.1.1. All three share the
single-source repo DefangLabs/pulumi-defang and use the same docs/
folder for overview and installation pages.

The previous single-schema entry (defang) is now obsolete — the provider
has been split into three cloud-specific schemas. Mark it DEPRECATED so
the publishing scripts skip it, and remove its cached content.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants