is there a way to update the stack config without running

pulumi up

. sort of like a reverse

pulumi config refresh

or something like what

pulumi config set --update-state foo bar

would do if it were a real command?

What would the effect be? If changing your config changes state (e.g.

pulumi config set numberOfSubnets 4

...) and you don't want to run

pulumi up

... what would it do?

Yeah good point, it's a weird ask. I would definitely want to run

pulumi up

shortly after the config update, but with the legacy systems i'm working with it's easier to update the config from one place, and then run pulumi up from a different place. Maybe I'll store this state outside Pulumi and pull it in the infra code then.