This message was deleted.

the way I've done it before is to have all your infra (so s3,

putStuffInBucket

etc) in one file, have the api gateway code in another, have the lambda code in another and then your index.tx can orchestrate it all together.

Thanks, @brave-planet-10645! Is there an example project that follows that paradigm in the examples repo that you know of by chance?

I've just put together a quick demo here: https://github.com/pierskarsenbarg/pulumi-demos/tree/main/s3-lambda

Thank you - this is very helpful!

I create all my resources in functions that take arguments and return

pulumi.Output

wrapped values for results, instead of top-level exports. Makes it much easier to mix & match your resources as needed (and no weird import-order dependencies).

@freezing-finland-22895 Can you please show an example of that?

I think this is what you're referring to: to use the value from an

Output

you can use apply and get to the value of it. It's because at run time we might not know what the value is (because the resource may not have been created yet) so you can use apply as a callback.

Here's a simple function that takes two arguments, representing a domain name and a subdomain, and creates a Route53 DNS record. The resulting fully-qualified name is returned as an https url. As @brave-planet-10645 mentioned, I used

apply

on the value of

resourcesDomain.fqdn

in order to construct the URL.

apply

is only necessary if you need to work with the value, tho. It could just as is easily return

fqdn

directly (which would still have type

Output<string>

). The key thing is that, by wrapping everything in a function, I control when these resources are created:

export async function createResourcesSite(apexDomain: string, apiDomain: string): Promise<pulumi.Output<string>> {
  const zone = await aws.route53.getZone({ name: apexDomain }),
    resourcesDomain = new aws.route53.Record(`...`, {
      type: "CNAME",
      ttl: 30,
      zoneId: zone.zoneId,
      records: [apiDomain]
    })

  return resourcesDomain.fqdn.apply((fqdn) => `https://${fqdn}`)
}

Hope that helps!

That is helpful, @freezing-finland-22895 - thanks! How would you go about setting up a lambda that required a provisioned resource within the Lambda itself? As an example, if I had a lambda that needed to know the id of a bucket or a connection string for Kafka to create messages? I like the functional approach, and that's the direction I've been going, but I end up doing something like:

// file 1
function x(bucketId) {
  return function y(event) {
    // connect to bucket
    // derive some data for bucket based on event input
   // return lambda result
  }
}

// file 2
// when creating the gateway, I end up something like:
const gateway = createApiGateway('gateway', [
    {
      path: '/',
      method: 'GET',
      eventHandler: x(bucket.id)
    }
  ]);

Do you run into similar scenarios, or are you grouping the creation of things like that inside your functions?

In the lambda function itself, you can access

Output

values using the

get

method. So if

bucket.id

has type

Output<string>

, then you could write:

function (bucketId: Output<string>) {
  return function y(event) {
    const bucket = bucketId.get()
  }
}

When the lambda runs (executes the body of

y

), then

bucketId.get()

will return the ID of the S3 resource.

Ok cool. I just wanted to make sure that using a pattern like that works. Thanks so much for your advice and example!