Inconsistent import behavior with `aws.ecs.Cluster`

When importing an existing cluster from my infrastructure, the only way to successfully do so has been using the name as the import key. For example if I have a cluster called MyCluster the construction of the cluster would look like this:

const existingCluster = new aws.ecs.Cluster(
            'pulumi-resource-name',
            {
                name: 'MyCluster'
            },
            {
                import: 'MyCluster',
                parent: this,
                protect: true
            }
        );

I am then putting this cluster in a crosswalk Cluster.

However, every time after importing the cluster this way, Pulumi tries to replace the cluster when a service is added to it. To fix this (after creating the stack), I changed the import key to be import: arnForMyCluster. Now when I got to deploy a new stack, that import statement is failing with the message.

Preview failed: refreshing urn:pulumi:staging::loop-lxp::loop-lxp:ecs:cluster$aws:ecs/cluster:Cluster::loop-lxp-cluster-existing-resource: error reading ECS Cluster (arn:aws:ecs:us-east-1:**account_id**:cluster/arn:aws:ecs:us-east-1:**account_id**::cluster/Loop): InvalidParameterException: Unsupported resource type: cluster

In opening this issue, I ultimately have two questions.

1. What is the correct way to import a cluster? Is it with the cluster name or its arn?
2. If it is with the cluster name, how can I keep that import statement with the cluster name consistent so new stack can be made, but not have pulumi try to recreate the cluster on every service change. I understand that might be a better issue to open up in crosswalk, but considering that its the non crosswalk import that is failing and being replaced, I figured I would start here.

Thanks for your assistance!

Package/runtime versions:

"node": 12.8.1,
"@pulumi/aws": "^2.0.0",
"@pulumi/awsx": "^0.20.0",
"@pulumi/pulumi": "^2.0.0",
"aws-sdk": "^2.667.0",
"typescript": "3.8.3"

[gunar]

You can import an existing ECS Cluster into Crosswalk:

const cluster = new awsx.ecs.Cluster("cluster", {
  cluster: networking.getOutput("clusterName"),
});

Here’s the full snippet:

// networking/index.ts
export const clusterName = cluster.cluster.name;

// application/index.ts
const env = pulumi.getStack();
const networking = new pulumi.StackReference(`…/networking/${env}`);
const cluster = new awsx.ecs.Cluster("cluster", {
  cluster: networking.getOutput("clusterName"),
});

[lukehoban]

I believe the questions raised here have been addressed. We also now support pulumi import which can be used in these cases. If there area any issues you are still seeing, please do open a new issue.