getting a strange error when running `pulumi impor...
# generalm
mammoth-art-6111
02/02/2022, 7:27 PMgetting a strange error when running
pulumi import aws:codepipeline/pipeline:Pipeline Copy code
error: aws:codepipeline/pipeline:Pipeline resource 'staging-pipeline' has a problem: expected length of stage.0.action.0.namespace to be in the range (1 - 100), got . Examine values at 'Pipeline.Stages[0].Action[0].Namespace'.e
echoing-dinner-19531
02/02/2022, 8:17 PMWe're actively working on this!
https://github.com/pulumi/pulumi/issues/7160
For now the only workaround is to write the resource in your program yourself and use
ResourceOptions.ImportIDm
mammoth-art-6111
02/02/2022, 8:23 PMi'm not familiar with
ResourceOptions.ImportIDmammoth-art-6111
02/02/2022, 9:02 PMmight be helpful to understand how you inform/connect pulumi to existing resources in the interim while these issues are worked out; i tried importing a few other resources and I wasn't able to import anything (as they all had derived/generated fields)
e
echoing-dinner-19531
02/02/2022, 9:09 PMechoing-dinner-19531
02/02/2022, 9:10 PMSpecifically on that page the part about the import resource option.
m
mammoth-art-6111
02/02/2022, 10:04 PMok; I think I understand, basically I have to manually define it and link the resource with the ID in AWS via
import👍 1
mammoth-art-6111
02/02/2022, 10:05 PMany idea on when the CLI import functionality will be fixed?
e
echoing-dinner-19531
02/02/2022, 10:19 PMWe hope to ship improvements in the next few releases.
echoing-dinner-19531
02/02/2022, 10:19 PMSo possibly next Wednesday, but if not I'd really hope we can make the two weeks after that (23rd Feb)
m
mammoth-art-6111
02/02/2022, 10:24 PMok, thank you for the update, trying to decide if we are going to use Pulumi for IoC and the import feature was really attractive.
4 Views