I have Team Starter edition which means my Pulumi org has no Pulumi ESC menu item. Can I still use environments to store secrets? My stack yaml file has

environment:
  - myproj/mystack

(Note that there's no myOrg, even though the stack is in myOrg.) My environment, viewed via

pulumi env --env myorg/myproj/mystack open

, shows this:

{
  "pulumiConfig": {
    "oauth": {
      "clientid": "x",
      "clientsecret": "x"
    }
  }
}

So I was hoping this would work:

const clientid = new pulumi.Config('oauth').require('clientid');

But I'm getting this error:

error: Missing required configuration variable 'oauth:clientid'
        please set a value using the command `pulumi config set oauth:clientid <value>`

Your environment should be like:

values:
  pulumiConfig:
    oauth:clientid: x
    oauth:clientsecret: x

From the output it looks like it's current like this:

values:
  pulumiConfig:
    oauth:
      clientid: x
      clientsecret: x

Yep that was it. Sorted now. Someone did explain to me what bits we do and don't have access to, way back when ESC was introduced. It probably has changed. But for now, I can keep building my poc; if it disappears, I'll just put the values into the regular config. It'll all go in a vault later anyway, if we get past the poc stage.

Hey @little-cartoon-10569 👋 nice to meet you. I'm Pablo, Engineering Manager for ESC First of all, thanks for the report, this does seems an inconsistency within our API that needs to be fixed, although I won't be happy if we break your poc 😄 Can you first tell me which org you are on and how long will you be working on it? So we might take that into consideration. Also, can you share, if you don't mind, if you have considered upgrading to use ESC in pulumi cloud? thanks!

iqa-managed-services is the org that I'm doing this work in. If we go with ESC, we'll likely create a new org; we use that org for small clients, but this piece of work is internal for my company, so if it goes ahead it will probably be separate.