mirror of https://github.com/pulumi/pulumi.git
101a72ed7f
Copilot templates require an access token to look up the conversation data and extract the code Here we try to download any template as usual, but then add the following logic to the response checking: - *If* a `403` is returned from what we identify as a pulumi-service backend (via `X-Pulumi-Request-ID` header, which has been present for the last 6 years) - *Then* we re-request w/ the auth token. If there is no token present then the login flow is automatically initiated. This does result in always raising a 403 on the server every time we request a copilot template. If we want to avoid these 403s we could check the domain against known pulumi backends in the CLI first, at the cost of intro'ing another code path. ## To test - Go through the Copilot flow, e.g "Create an s3 bucket please" - Click "Deploy with Pulumi" - Choose CLI, click next - Check out this branch - Copy most of the command but first: `cd ~/pulumi/pulumi/pkg` and then `go run ./cmd/pulumi new $ARGS_FROM_PULUMI_CLOUD_UI` It should succeed |
||
---|---|---|
.. | ||
auto | ||
common | ||
internal | ||
property | ||
pulumi | ||
pulumi-internal/netutil | ||
pulumi-language-go | ||
pulumix | ||
Makefile | ||
README.md |
README.md
Pulumi Golang SDK
This directory contains support for writing Pulumi programs in the Go language. There are two aspects to this:
pulumi/
contains the client language bindings Pulumi program's code directly against;pulumi-language-go/
contains the language host plugin that the Pulumi engine uses to orchestrate updates.
To author a Pulumi program in Go, simply say so in your Pulumi.yaml
name: <my-project>
runtime: go
and ensure you have pulumi-language-go
on your path (it is distributed in the Pulumi download automatically).
By default, the language plugin will use your project's name, <my-project>
, as the executable that it loads. This too
must be on your path for the language provider to load it when you run pulumi preview
or pulumi up
.