PatchUpdateCheckpoint is what the HTTP backend uses today - it:
- Takes a full
UntypedDeployment(complete snapshot) - Writes it immediately to Pulumi Cloud
- Is idempotent (can retry safely)
- Requires an active
UpdateIdentifier
| apiVersion: argoproj.io/v1alpha1 | |
| kind: Application | |
| metadata: | |
| name: kubernetes-py-guestbook | |
| namespace: argocd | |
| finalizers: | |
| - resources-finalizer.argocd.argoproj.io/background | |
| spec: | |
| project: default | |
| destination: |
| package workqueue | |
| import ( | |
| restate "github.com/restatedev/sdk-go" | |
| ) | |
| // WorkQueueExample is an example workflow that demonstrates how to use the FixedWorkQueue as a blocking queue. | |
| // The workflow enqueues an abstract "work item" to the queue, waits to be scheduled, does some work, and then | |
| // notifies the queue. The "work" in this case is simply waiting for a callback to be invoked. | |
| // |
PatchUpdateCheckpoint is what the HTTP backend uses today - it:
UntypedDeployment (complete snapshot)UpdateIdentifierA standalone MCP server that provides direct access to Pulumi provider CRUD operations, bypassing the Pulumi engine. This enables ad-hoc infrastructure management by leveraging existing Pulumi providers through the Model Context Protocol.
| # mise configuration for pulumi-azure-native | |
| # Auto-generated from Makefile and CI scripts | |
| [tools] | |
| # Core Languages (versions from .github/actions/install/action.yml) | |
| go = "1.24.7" # From provider/go.mod | |
| node = "20" # From CI: actions/setup-node@v4 | |
| python = "3.9" # From CI: actions/setup-python@v5 | |
| java = "temurin-11" # From CI: actions/setup-java@v4 | |
| dotnet = "8" # From CI: actions/setup-dotnet@v4 |
Create a v2 branch to enable patching v2.x releases while master continues with v3.x development. The last v2 release was v2.90.0 (commit 9ab68b7632627d5c5a7ad2d1d27dac99712fe429, March 27, 2025).
Key Principle: Minimize differences between v2 and v3 workflows. Both branches use azure-native's custom workflows (not ci-mgmt). A future ci-mgmt migration can be done for both branches together.