https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
g
I'm not familiar with that error message, but did you also update 
awsx
? That 
urn
indicates you're using 
awsx
as well.
a
awsx is on latest 0.18.10
I can provide full yarn.lock over dm if needed
b
This is the part that's incorrect
arn:aws:ecs:us-east-1:149539663033:cluster/arn:aws:ecs:us-east-1:149539663033:cluster/blah-cluster-qa-6372e69
it's added the full ARN to the end of the ARN where it should have added just the cluster name
Please can you open a bug in pulumi-awsx @adamant-dress-73325?
We need to look at this for you
a
@broad-dog-22463 Sure, I'll open an issue
b
Thanks!
a
l
Hi @adamant-dress-73325 it is possible to show a few lines of the code where you create this cluster?
a
Copy code
const cluster = new awsx.ecs.Cluster('cluster', {
    cluster: stackRef.getOutputSync('clusterId') as pulumi.Output<string>,
    vpc,
  });
l
interesting. and where's the code that exposed that 
clusterId
variable?
a
Copy code
cluster = new awsx.ecs.Cluster(`pt-cluster-${env}`, {
    vpc: vpc,
    tags: {
      Name: `pt-cluster-${env}`,
    },
  });

export const clusterId = cluster && cluster.id;
l
that all looks proper. in the pulumi console, for the stack where you export clusterId, what does it show as the value in your Outputs
i.e.
trying to narrow down where things are going off the rails.
a
one sec
@lemon-spoon-91807 Will dm you instead
l
sure
@broad-dog-22463 i can't see anyhting on our end that is immediately wrong. and i've found this:
where someone reported the same issue. i.e.:
(arn:aws:ecs:eu-west-1:104375939617:cluster/arn:aws:ecs:eu-west-1:104375939617:cluster/candu-backend): InvalidParameterException: Invalid identifier: Unexpected number of separators
which is the exact same issue here (where a portion of the arn is prepended to the real arn)
going to spelunk into the terraform code.
pulling @microscopic-florist-22719 In. Pat, i have investigated this and there appears to be nothing wrong on the SDK side here. Either something is going off the rails on the engine side (seems unlikely) or this is a terraform issue (though i couldn't find a smoking gun.
While investigating with @adamant-dress-73325 we isolated things down to just a simple call to:
aws.ecs.Cluster.get("whateveryouwant", "< their actual cluster id >")
this call fails with AWS reporting back that the cluster ID is malformed. looking at our logs we have:
ReadResource RPC prepared: id=<correct id>, name=whateveryouwant<{%reset%}>)
however, aws reports back effectively:
arn:aws:ecs:us-east-1:149539663033:cluster/arn:aws:ecs:us-east-1:149539663033:cluster/blah-cluster-qa-6372e69): InvalidParameterException: Invalid identifier: Unexpected number of separators
basically, something in the engine/provider/terraform has taken the ID up through the 
/
and has prepended it to the beginning of the ID.
all other reads are succeeding, so i can't imagine this is on us.
but i also don't see anything in terraform that would cause this
but it was closed out, and no-one else has reported this problem
i'm at an impasse on how to proceed @microscopic-florist-22719. Do you have any ideas?
Richard also says: ok, I can repro again if necessary, this still happened after a full rm -rf of node_modules so should be reproducible
he's ok for now moving back to 0.18 libs. but this is a pretty worrying issue in the 1.1 libs.
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by