https://pulumi.com logo
#general
Title
# general
l

limited-rainbow-51650

08/19/2021, 6:49 AM
I just read the
August 18
release blog article: https://www.pulumi.com/blog/pulumi-release-notes-m60/#dependson-now-works-for-pulumi-component-packages-and-more In the linked section on
dependsOn
, I read this:
Copy code
Now, depending on a Pulumi Component Package's component will always wait on all of that component's children, regardless of language.
A
ComponentResource
and a Pulumi Component Package are 2 different things. Does this change impacts the dependency management of a
ComponentResource
?
m

microscopic-pilot-97530

08/19/2021, 7:47 PM
Does this change impacts the dependency management of a 
ComponentResource
?
Yes, the Python and Go SDKs were changed to match the behavior of Node.js and .NET: Depending on a component implicitly depends on all of the component’s children. https://github.com/pulumi/pulumi/pull/7732 https://github.com/pulumi/pulumi/pull/7737
e

enough-garden-22763

08/19/2021, 7:49 PM
I’m trying to learn all these terms too, so please bear with clarifying. Component Packages are defined in
<https://www.pulumi.com/docs/guides/pulumi-packages/>
so
Write a Pulumi Component in your language of choice and expose it to users in all Pulumi languages
. Was there not a change also to tracking dependencies of resources and components from a Component Package (internal lingo for these is “remote”).
m

microscopic-pilot-97530

08/19/2021, 7:50 PM
Was there not a change also to tracking dependencies of resources and components from a Component Package (internal lingo for these is “remote”).
Yes, that was fixed as well.
e

enough-garden-22763

08/19/2021, 7:50 PM
This must have been earlier https://github.com/pulumi/pulumi/pull/7541 in 3.7.1 (2021-07-19)
Sorry for the confusion.
2 Views