This message was deleted.

sparse-intern-71089

07/20/2023, 4:04 PM

This message was deleted.

salmon-account-74572

07/20/2023, 4:15 PM

Hey Michael, sorry you’re running into an issue. I’ve contacted our AWS Native provider team internally to see if I can get some additional information for you. You’re probably already aware, but the AWS Native provider doesn’t (currently) have the same breadth of coverage as the AWS Classic provider, and so it’s possible you may need to use a combination of AWS Native and AWS Classic in your Pulumi programs (this is not uncommon and is fully supported).

polite-napkin-90098

07/20/2023, 4:43 PM

Thanks Scott, much appreciated I am, indeed, doing that, but the aws-native one seemed to work fine for ECS services. it's just this import that's stumping me.

salmon-account-74572

07/20/2023, 4:54 PM

Gotcha. As soon as I get some more information from the AWS Native provider team, I’ll update you here.

🙏 1

polite-napkin-90098

07/27/2023, 7:03 PM

any news on this, I ran into it again today

polite-napkin-90098

08/02/2023, 7:15 PM

I found a confusing but potentially helpful part of the help text on the

pulumi import

cli.

Copy code

--properties strings                    The property names to use for the import in the format name1,name2

I say potentially helpful as the error above also talk about properties, but I've no idea how to use it as there are no examples in any of the docs I can find. Does anyone know what this flag is for and what strings I'm meant to pass it? I tried:

pulumi import --provider urn:pulumi:test-ecs-recorder::infra-ecs-recorder::pulumi:providers:aws-native::test-ecs-recorder-nativeProvider -s test-ecs-recorder --properties ServiceArn,Cluster aws-native:ecs:Service recorder arn:aws:ecs:us-east-1:#####:service/Test/recorder,Test

but that gives the same error as above. Are there good docs for the CLI somewhere I'm missing?

polite-napkin-90098

11/16/2023, 5:21 PM

I never received a reply to this and am running into it again today. Can anyone help?

gifted-gigabyte-53859

11/17/2023, 2:28 AM

I'd suggest trying the imports with aws classic. Although deploying things with native worked, imports can be slightly different in my experience

polite-napkin-90098

11/30/2023, 7:54 PM

So import it with classic and then switch them from one provider to another?

salmon-account-74572

11/30/2023, 9:47 PM

I don’t think that will work (the provider is in the URN for the resource).

polite-napkin-90098

04/25/2024, 7:20 PM

I'm wondering if there's been any update from the aws-native team on this issue? I'm trying to import another ECS service and running in to the

api error ValidationException: Identifier ... is not valid for identifier [/properties/ServiceArn, /properties/Cluster]

I've been asking the Pulumi AI but all its suggestions e.g. `

Copy code

pulumi import aws-native:ecs:Service ld-relay "Production:ld-relay"

Copy code

pulumi import aws-native:ecs:Service ld-relay arn:aws:ecs:<region>:<account-id>:cluster/<cluster-name>/<service-name>

and a number of variations thereon give the above error. I'd really like imports to work in aws-native

enough-garden-22763

04/25/2024, 7:32 PM

Hi Michael, do you have it tracked in https://github.com/pulumi/pulumi-aws-native I can bump it so we take another look? Thanks

polite-napkin-90098

04/26/2024, 9:14 AM

I haven't added it there, yet, I wasn't sure if it was a bug or just a lack of documentation, but I guess in either case I can add it there. I'll do so later today.

enough-garden-22763

04/26/2024, 2:08 PM

Thank you! That helps a lot

calm-keyboard-75974

07/09/2024, 12:11 PM

I figured this out after having a similar problem, according to https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/resource-identifier.html you need to specify multiple identifiers using the pipe delimiter, so your example would be

pulumi import aws-native:ecs:Service ld-relay "<service-arn>|<cluster>"

🙌 1

🙏 1

👀 1

gifted-gigabyte-53859

07/10/2024, 12:25 AM

fyi @polite-napkin-90098 @salmon-account-74572

13 Views

Open in Slack

Previous Next

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.