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

Oh... I thought I got an error when tried to use `request` from the top of the file the other day. Yes, the code that runs once on warm-up, to reuse HTTP connections.

there are a couple of things that you can do here.

first, you can import the module like normal, then reference it inside your functions.

second, if you want to run warmup code, we have a mechanism ofr that as well, but i'd need to see your scenario/code to give advice on how to deal with this

basically, we have something we call a "factoryFunction" which runs once when the Lambda/Module loads and has time to set things up and then define the actual entrypoint function that will trigger each time the Lambda is hit.

The scenario is simple:
```
// do once
const http = require("http");
const httpAgent = new http.Agent({ keepAlive: true });
// do at invoke
request({ url: url, pool: httpAgent }...
```

so i may lose connection and be offline a while

not a totally clear example, but here's a start: <https://github.com/pulumi/pulumi-cloud/blob/f4f7ced450b1a57821c6cdbbd6c61b8770763641/aws/httpServer.ts#L39-L50>

this is no-arg function that, whne invoked, will produce the actual Lambda entry function.

you can see we pass that no-arg function to createFactoryFunction

<https://github.com/pulumi/pulumi-cloud/blob/f4f7ced450b1a57821c6cdbbd6c61b8770763641/aws/function.ts#L25-L28>

which basically just passes hte isFactoryFunc bool down

as you descend downwards into the lower level pulumi code, it understands how to properly generate this so you basically get:

`module.exports = factoryFunc();` instead of `module.exports = func;`