This message was deleted.

Is exporting outputs from your Pulumi program not doing everything you need? Can you describe your intended flow?

I want to take the output of creating some resources and create a dynamodb TableItem with the contents

You want to use outputs in the JSON going into the TableItem? You need to either 1) create the TableItem inside an

apply()

, or 2) create the TableItem outside your Pulumi program, possibly in another program, in another inline automation-api program, or outside Pulumi altogether, using the normal DynamoDB SDK or API.

The docs omit

pulumi.Input

from all input types just because of redundancy but they're always `Input`s. It would probably make sense to have some sort of one-liner to that effect in the docs though.

They're not always Inputs though. They should be, but there are some places where it's been missed.

Like what? I know the resource_name is a

str

but other than that I didn't know that that was a thing.

I thought I saw somewhere in the docs that you shouldn't create resources within apply() ?

You shouldn't, if you can avoid it. And you can avoid it this time. You need to build your JSON string inside an apply, but you can pass the result to TableItem's args.item.

gotcha!

Something a bit like this (where foobar is an output on a resource you've created):

const item = resource.foobar.apply(foo => JSON.stringify({ "key": `${foo}bar`})); // item is a pulumi.Output<string>
const ti = new aws.dynamodb.TableItem("ti", {
  tableName: table.name,
  hashKey: table.hashKey,
  item: item
}, opts);

oh! that makes sense. Thanks for the example.

Your options there are to chain your calls to

apply()

, or use

pulumi.all()

.