I have a weird issue and I don’t know if this goes in #aws, here, or elsewhere but here goes. I built a stack in python that mimics what we currently do with Cloudformation to deploy a Fargate app, reusing outputs from a base networking Cloudformation stack that provides VPC, subnets, load balancers, listeners, DNS zone etc… I built it using a combination of

aws

and

aws-native

providers, preferring the native one where available and working. it works fine, outperforms cloudformation as expected I then moved that exact same code into a new file and wrapped it in

class MyCustomFargateApp(pulumi.ComponentResource):

I passed `opts=pulumi.ResourceOptions(parent=self)`everywhere, and that’s all the changes I did when I tried to deploy it, I got this error:

Diagnostics:
  pulumi:providers:aws-native (default_5_7_0):
    error: no resource plugin 'pulumi-resource-aws-native' found in the workspace at version v5.7.0 or on your $PATH, install the plugin using `pulumi plugin install resource aws-native v5.7.0`

which makes no sense because

aws-native

is in v0.18.0 and it’s

aws

that’s v5.7.0 to debug: • I nuked venv and

__pycache__

• I changed the name of the stack in Pulumi.yaml • I removed both providers using

pulumi plugin rm resource aws

etc the results are the same I did the same steps with the working stack without a ComponentResource, it deploys fine from scratch I repeated the same steps with my broken stack but I commented out *every resource*… it deploys fine, just shows an empty MyCustomFargateApp resource. swell. I then proceeded to remove comments from resources one by one. working fine: • pulumi_aws.route53.Record • pulumi_aws.iam.Role • pulumi_aws_native.logs.LogGroup • pulumi_aws_native.ecs.TaskDefinition • pulumi_aws.lb.TargetGroup it blows up when I uncomment the pulumi_aws_native.elasticloadbalancingv2.ListenerRule it does reference the TargetGroup which comes from aws-classic… but exact same stuff works if not wrapped in a ComponentResource please advise, I’m losing my mind

Hmm... While I'm digging in and trying to figure out what might be going on, can you let me know whether, when you say you moved the exact same code into a new file, whether the file is in the same project (the same directory) as the working stack?

I created a new directory in the same project, and pasted the code into a file called

__init__.py

😂 it's all good; I know what you mean

so I moved the code into

mycomponent/__init__.py

and then wrapped it in `class MyCustomFargateApp(pulumi.ComponentResource):``

And are you calling

pulumi up

(or preview) from the root, or from

mycomponent

?

and then in the original file

__main__.py

I referenced it as:

app = mycomponent.MyCustomFargateApp(ServiceName, ImageUrl, HealthCheckPath, DesiredCount=DesiredCount, AppListenPort=AppListenPort)

gotcha. One sec, let me check something

I fixed the issue by replacing with

pulumi_aws.lb.ListenerRule

oh, wait, really?

yeah it’s fully deployed and app is running 😄

iiiiinteresting

yeah but aws.lb is ew 😄

But do you mind if I pass this info along to the folks responsible for the native provider and see if there's a bug?

yup

Because that doesn't make much sense on its face overall that it would fail, but I suspect it could be because the native provider is still in beta and there could be a bug on the other side

I don’t mind sharing code directly with folks, I’d rather not post it publicly tho

👍 thanks! I'll let you know what I find; might be a day or two

want the entire project zipped?

not yet 🙂 Let me see if they've got a "ah-hah, but there wasn't X" kind of answer first

can you do a

pulumi stack export

(which should give you a JSON representation of the entire project) and look through it for the offending resource? it should have a provider associated with it

this happens before the resource has deployed tho

Can you share the full code?

will do, just documenting a few more cases first

Are you setting an explicit provider when you call the component? Can you file an issue for this please

yup, was just building a repro case

Wow, catching up this morning, and that's an interesting bug. Thank you so much for digging in!

:)) thank you for showing interest yesterday, i probably wouldn’t have continued chasing it if it was just dead air

@damp-fall-55922 because of your awesome thorough bug report, we were able to get a fix written very quickly: https://github.com/pulumi/pulumi/pull/9802 Can you DM me or Laura your email? We'd like to send you a t-shirt as a thank you