Justin Van Patten

Reopening because we reverted the fix in https://github.com/pulumi/pulumi/pull/16131 due to https://github.com/pulumi/pulumi/issues/16126.

Note that https://github.com/pulumi/pulumi-dotnet/issues/292 needs to be addressed before we bring this back.

Thanks for opening the issue and sorry for the trouble! I was able to reproduce the same behavior with a `Bucket` resource in AWS. I would expect the resource to...

> - [ ] Explore/spike on generating copyable resource constructors (minimal and complete) > - [ ] Explore/spike on generating copyable lookup functions I think both of these are covered...

> > * [ ] Add and populate a new field to the schema for copyable resource constructors > > * [ ] Add and populate a new field to...

Thanks for digging into this, Pat! > `pulumi/pulumi/sdk` could then freely depend on `pulumi/esc` and `pulumi/pulumi/pkg` could depend on `github.com/pulumi/esc/cmd/cli`, all without circularity. This would be ideal. If others find...

https://github.com/pulumi/pulumi-hugo/blob/ec2b6fed8fd7c58cc8d397ac1fed3f20ec170f79/themes/default/content/docs/concepts/config.md?plain=1#L617C116-L617C146 Wondering if "Pulumi ESC" should link to some kind of overview page for Pulumi ESC that explains what it is.

Some things that should be updated as I was reading through the page: --- https://github.com/pulumi/pulumi-hugo/blob/ec2b6fed8fd7c58cc8d397ac1fed3f20ec170f79/themes/default/content/docs/concepts/secrets.md?plain=1#L82-L83 ``` - Setting `configuration.${KEY}.Secret: true` when reading a value from the config. - Calling `Fn::Secret`...

@pcyang, out of curiosity, why aren't you checking in `Pulumi.MY_STACK_NAME.yaml`? The `secrets-provider` option primarily exists for use with the `upsert` option (see https://github.com/pulumi/actions/issues/338): > `upsert` - (optional) Allows the creation...

You can set the config via `config-map`, e.g.: ```yaml config-map: '{name: {value: my-user-name, secret: false}, {foo: {value: bar, secret: false}}' ```