This message was deleted.

I don't see that behavior mentioned in the documentation, either

It's odd that it does that. Can you confirm that you don't have a resource or stack transformation that clears the name input? All other resources use name as an input specifically to stop Pulumi from generating unique suffices.

This is literally the entire code block?

That said, it should be feasible to get the actual randomized name from Pulumi for use in your pipelines. You can push the name to somewhere in your CI system, or have your pipeline grab the name from the stack references. I know that well-known, widely-advertised names are often important or even essential, but the random suffix is really useful to allow Pulumi to always-on redeployments.

can you give me a hint as to what I would be looking for then? I'm still very new to this.

The name you're setting is the Cluster settings name, not the Cluster name.

the word transformations is no where in my index.ts, so not doing those based on the docs I just looked up

It's not a transformation issue. You're just not setting the name. Try this:

const hsnext_prod_east_cluster = new aws.ecs.Cluster("hsnext-prod-east-cluster", {
  name: "hsnext-prod-east-cluster",
 settings: [{
    name: "containerInsights",
    value: "enabled",
}]});

Ok. Yeah, I literally copied the example in the docs

You need to set the name property to get Pulumi to use it literally. The name parameter is used as the prefix of the default name; the name property eliminates the default name and uses what you configure.

gotcha. So yeah, that's probably what's wrong with Service as well

There are good reasons to let Pulumi do the naming, but if you have better reasons not to allow that, then use the name property.

Thanks!