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.

Pulumi Community

the pipeline does have "name" defined and it satisfies that regex

also doesn't seem to be nested, so it's not the name of an action or anything

i tried running it with verbose mode tuned all the way up and got nothing interesting

or at least, i couldn't find anything interesting personally

if i back up and try to just create the pipeline - i.e, not import it - it just works

so i'm wondering what it's pulling to validate `name`

i grabbed the codebuild definition from AWS CLI and that name should statisfy the regex, and again, it doesn't look like action[0].name or anything so... seems like it's actually complaining about the codebuild name that AWS is giving it?

is it possible the regex being satisfied is not the one spit out?

yeah, not sure what's going on here, tried it on a different pipeline with a very simple name and i got the same error

the strange thing is this is happening only because of import; if i use the same definition, change the URN/name and deploy, it deploys

Sorry this took me so long to get to. Can you drop the code for the resource with the import statement (with confidential info redacted) in here so I can take a quick pass before passing you to the bug report link?

i also have the response from AWS CLI at the same time

just got the same error. different pipeline

That's definitely odd. Head to <https://github.com/pulumi/pulumi/issues/new?assignees=&amp;labels=kind%2Fbug&amp;template=0-bug-report.md>, and can you drop me a link here so I can ensure it gets tagged for the triage team?