dad7f2c2f0
Config values that are objects are represented in memory as JSON strings. When a config map is being saved to a file, object values are first unmarshaled from JSON to `interface{}` and then the entire config map is marshaled to YAML (or JSON) and saved to disk. When an object value is unmarshaled from JSON, any numbers in the JSON string were being implicitly unmarshaled as `float64`, which resulted in some numbers in the nested objects being emitted in YAML using exponential notation (e.g. a number `12321123131` in an object value was being saved in the YAML as `1.2321123131e+10`). To address this, when unmarshaling the JSON for an object value, first try to unmarshal any numbers as `int64`, falling back to `float64`.
|
||
|---|---|---|
| .. | ||
| auto | ||
| common | ||
| pulumi | ||
| pulumi-language-go | ||
| Makefile | ||
| 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.