This message was deleted.
# getting-started
s
This message was deleted.
p
usually, you’re gonna have issues if you try to pass
Output<X>
to functions that do not expect
Input<X>
Output<X>
is a wrapper for type
X
and it’s necessary because the value might not be available at the beginning (because for example it comes from other cloud resources created dynamically)
can you share some reference what resource you’re talking about?
I’ve found https://www.pulumi.com/docs/reference/pkg/aws/ecs/taskdefinition/ but there’s nothing called
logConfiguration
.
so it’s possible you will need to generate
logConfiguration
value using pulumi
apply
function
assuming you have
Output<string>
called
mySecret
you should write (treat it as a hint and not a working example - I usually use python with pulumi):
Copy code
...
logConfiguration: mySecret.apply(s => {
  foo: "bar",
  options: s
}),
instead of:
Copy code
...
logConfiguration: {
  foo: "bar",
  options: mySecret
},
m
thanks for the response @prehistoric-activity-61023. The suggested change worked
🙌 1
sorry for the delayed response I didn't notice it earlier