This message was deleted.

So this kinda worked, but when running up it would often get things wrong in the preview, as in say it was going to delete things and then update them, or say it would update things and then not. My colleague who understands apply and promise somewhat better than me, spent some hours working on trying to fix it and claims that it isn't possible and there is nothing we can do but set the config options in every stack. Is he right?

It was true. But a recent update allows stack outputs to retrieved as non-futures, which will allow this. See

getOutputDetails()

here: https://www.pulumi.com/docs/intro/concepts/stack/#reading-outputs-from-stack-references

thanks for the link @little-cartoon-10569 yes the stacks I mention are in their own projects, so I am looking at passing config across projects, I guess it could be global, especially as we're only in a single cloud at the moment, but having it being inheritable so e.g. all the AWS stacks inherit it from their parent stack and the Google stacks from theirs. I'll have a read of that link and see if it helps me.

You can have a global project whose stacks do nothing but provide configuration for other projects (usually, grabbing config from a stack of the same name). However, you can do exactly that with a solution that does not depend on the Pulumi service, thus cutting out web traffic and potential for failure