This message was deleted.

you're exporting the whole cluster object, which won't work because stack outputs are only primitives like strings - but luckily the FargateService constructor's cluster argument is only supported to be the arn, which is a string

Hi @ancient-car-89914 Thanks for your response. The

cluster

argument which is part of the

awsx.ecs.FargateService

is looking for a value of type

awsx.ecs.Cluster

and thus the

arn

value is not being accepted. I guess your suggestion will work with the classic aws api

aws.ecs.Service

since it is only looking for

string

for the

cluster

argument.

ah, my mistake - I haven't yet worked with the native providers, I guess you would need to get the cluster by its arn somehow

Unfortunately i could not find any method in

awsx.ecs

to fetch the cluster which returns the type of

awsx.ecs.Cluster

😢 Will probably have to create the service using

aws.ecs.Service

i guess

Just as @ancient-car-89914 said above, you cannot export the whole cluster object.You could export its

name

instead. I am assuming you are using AWSX

0.x

? In that, the

awsx.ecs.Cluster

accepts a

cluster

arg which can either be an

aws.ecs.Cluster

or an

Input<string>

(the existing cluster's name): https://github.com/pulumi/pulumi-awsx/blob/066dcd47e78198a9a56ea36a38b4615ac50c747e/awsx-classic/ecs/cluster.ts#L176. So use the

name

from your other stack to "re-create" the Cluster resource. Note that when you do this, you are essentially bringing the cluster resource into this stack's state. This is because AWSX does a

.get()

when you pass the name thereby bringing the cluster into the state. So it's sort of undoing the separation that you are likely looking to have.

Thanks for the input @clever-sunset-76585 It will give these a shot and see if it solves my issue