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

would the following be adviseable:
```const region: aws.Region = new pulumi.Config("aws").require('region');```

<@U034YM8SUSW> you'd need to use an `apply` for this, as the config is retrieved async

also, the config setting is global, so unless you need an explicit provider you probably don't actually need to do this

it appears to work without using apply. Is the recommendation to use apply in order to get it functional or to avoid some sort of undesirable side effect?

it may not always behave as expected, but if it works that's great. if you see anyweird behaviour, let us know

<@UCWG26BH7> <https://www.pulumi.com/docs/intro/concepts/config/> doesn't have any examples using `apply`, they're all using plain `require*()` or `get*()`. Is the need for `apply` an omission in that documentation?

<@U03511M1C04> the examples show you how to retrieve a configuration item from the config stack. the values as retrieved as `Input&lt;T&gt;` and usually, you'd pass those values to another resource which take an `Input&lt;T&gt;`

However, if you need to pass a value to a resource which is a string, you'd need to use an `apply` It looks like the region can be tInputty typein this case, so an apply is not needed, I should have checked before commenting