I'll have to see. On most everything else I have explicitly named them
e
echoing-dinner-19531
05/22/2023, 8:55 AM
Sorry was on holidays last week, only just seen this.
I suspect you might need to alias things because adding a new component will have changed the resource URNs (they include some parent information in them) and the URN is used to determine replacements.
g
great-sunset-355
05/22/2023, 1:21 PM
I hope you enjoyed your holiday :)
I downgraded pulumi from 3.6x back to 3.47.1 and the problem was gone. I will report again when I get the chance to upgrade.
Originally I tried to create a ComponentResource with --target to create an empty resource and then import existing resources into it. However the creation of the component caused unexpected replacement on seemingly unrelated resources. I did not have much time to investigate thoroughly and the downgrade was the fastest workaround.
e
echoing-dinner-19531
05/22/2023, 1:22 PM
Ah there have been some issues around --target recently so you may have hit one of those. I don't think there's any outstanding known about bugs around that right now but if you do hit anything odd let us know and we'll investigate.
g
great-sunset-355
05/22/2023, 1:26 PM
Will do, thank you.
Just remembered that the problem appeared after importing the first resource inside the component.