Fraser Waters

Reopen to track adding to the schema (somehow)

N.B Some of this is now covered by the [command package](https://www.pulumi.com/registry/packages/command/) We're still thinking about how to do sequenced actions with just program code so you don't have to resort...

Just noting down an example from a friend using DigitalOcean that fits into this idea of sequence actions. They we're trying to create a [CustomImage](https://www.pulumi.com/registry/packages/digitalocean/api-docs/customimage/) which needs a url to...

> (unless there is a very good reason we can't), We already have a few resource options that we allow to be Outputs today (e.g. alias names). I want to...

> (e.g. a provider that you get from an MLC) I wonder if it's more possible to fix that so they aren't outputs? My guess is that we could probably...

@t0yv0 recently left a comment on a related ticket to this: https://github.com/pulumi/pulumi/issues/3364#issuecomment-1267034580 Just to leave some hope and direction for this ticket now that the suggestion of `tryGet` looks to...

Note this might be related to https://github.com/pulumi/pulumi/issues/9107 as well, its mostly auth tokens and similar that change a lot and don't really need diffing.

This is probably fine, but I'd suggest waiting till we come back from refresh week before merging just in case integration test workflows don't like it.

Those `stack.up` calls aren't in parallel, one's awaited before starting the other so I don't think this is the same as #5549

I am not convinced that this is a good change. These strings are single use strings, there's no need for them to be named at all. Better to be inlined...