No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Which config?
Everything I've encountered has types already

e.g. `export const x_name = resource.name;`

I mean the stacks config, which u can set in the yaml file. 

Pulumi.stack.yaml

I'm not aware of any way to gen a type from this (though there's proably an online tool)

What I do though, is hand craft a type and then require all the values into this and use it in a multi-stack

sorry, that may not be too helpful to your case

Does the cli validate the User provided types for the config

```//StackConfig.ts

//...//
export type CommonConfig = {
  vNetCidr: string;
  numProp: number;
  secretValue: Output&lt;any&gt;;
  internalProp: string;
  //...//
}

//CommonConfig.ts
export = async () =&gt; {
  const config = new pulumi.Config();

  const out: Omit&lt;CommonConfig, "internalProp"&gt; = {
    vNetCidr: config.require("vNetCidr"),
    numProp: config.requireNumber("numProp"),
    secretValue: config.requireSecret("secretValue"),
  };
  return out;
}```


basically, I have a config stack which only holds my config, then I import that into any stacks that require config settings

via stack ref
<https://www.pulumi.com/docs/tutorials/aws/aws-ts-stackreference/>

Thanks that code snippet definitely helped. I was trying to think of a way to import the whole config in a type by using adding the template type in config.require. 
But it's probably better to construct a hand crafted config object.

it's not the best, i'd be interested in a better way

currently, to add a new config value, I have to edit it in 4 places, not very DRY at all :slightly_smiling_face:

Four places, so the first is the yaml file, second is the config type, third would be requiring the new config value, what's the fourth one

In the stack reference I have to do the extremely similar function as to the config require
```appApiEndpoint: await stackRef.requireOutputValue("appApiEndpoint"),
appCallbackUrls: await stackRef.requireOutputValue("appCallbackUrls"),```