History

Will Jones 4e90fcb781 Implement the `CreateIfNotExists` resource option This commit implements `CreateIfNotExists`, a new resource option that allows programs to specify resource options that should be created only if they do not already exist in the provider. Use cases for this feature include "global" or shared resources, such as AWS service-linked providers within an account, or SSL policies within a GCP account/project. `CreateIfNotExists` behaves as follows: * The option accepts an ID, much like `Import`, that will be used to determine whether or not a resource exists using a `Read` operation. If it does, resource inputs must match as they would be required to in an ordinary import. If not, the resource is created as usual. * Due to the semantics specified above, it is an error to specify both `CreateIfNotExists` and `Import` resource options on a single resource. The "if not exists" part is handled by a provider `Read` call that we make in step generation. This is not ideal, since we'd like step generation to be non-blocking (and `Read` could block for an arbitrary amount of time). However, there aren't many other good options for achieving this: * Source evaluation would be a good middle ground, but this would require changing the contract of `Read`/introducing another call since we do not have a URN at this point. * Parallelising step generation (see e.g. #15026). This is the "best" outcome and feels the most correct, but carries a large amount of risk. There _are_ instances of us breaking this rule (not blocking in step generation) already (e.g. `Check` and `Diff`, which "should" be fast but in reality could do anything they like), and the hypothesis is that there won't be many resources with this option in a given stack, so this feels like an acceptable compromise. A set of lifecycle tests capturing `CreateIfNotExists`' interactions with existing resource options and scenarios are included. This commit does not include SDK updates to use the new option; these will be introduced in future changesets. Part of #16189		2024-07-02 17:27:42 +01:00
..
auto	Protect access to transport.UnsupportedCapabilities inside repo.FetchContext (#16517 )	2024-06-28 23:17:26 +00:00
common	Implement the `CreateIfNotExists` resource option	2024-07-02 17:27:42 +01:00
internal	turn on the golangci-lint exhaustive linter (#15028 )	2024-01-17 16:50:41 +00:00
property	Property map keys are just strings (#15767 )	2024-03-25 17:26:41 +00:00
pulumi	Implement the `CreateIfNotExists` resource option	2024-07-02 17:27:42 +01:00
pulumi-language-go	Changelog and go.mod updates for v3.122.0 (#16551 )	2024-07-02 07:54:27 +00:00
pulumix	Use EqualError/ErrorContains instead of Error (#14737 )	2023-12-08 06:40:14 +00:00
Makefile	make(sdk/go): Use -C instead of cd for 'go' commands (#13853 )	2023-08-31 21:12:03 +00:00
README.md	`pulumi update` => `pulumi up` (#2702 )	2019-05-06 14:00:18 -07:00

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.