Can I specify the pulumi organization in

Pulumi.yaml

, in order to prevent accidental resource instantiation into an incorrect Pulumi org? For a consultant who manages Pulumi projects for several customers with separate Pulumi organizations, but all under his/her single email address, it seems unreasonably precarious to rely on correctly setting environment variables before running Pulumi commands.

this isn't currently possible, but it's very valid and a good feature request. Could you cut an issue in github.com/pulumi/pulumi