https://pulumi.com logo
Join Slack
Powered by
How should I exactly understand this tree? I'm usi...
# general
g
How should I exactly understand this tree? I'm using it to spawn vm's in proxmox through the package and then bootstrap a talos kubernetes cluster. but i feel like my 
dependsOn
needs some tweaking. 🤔
e
The tree view shows child/parent relationships (set via the Parent resource option). It does not show dependencies in general. So only worry about tweaking your dependsOn if you've got a real dependency that isn't expressed by the input values and it's causing deployment issues.
s
If you want to see the dependency graph, you can try using 
pulumi stack graph FILENAME
or check the UI's graph view for the stack under the resource list
g
so, what the more deep 
dependsOn
i use, the bigger the tree? is it overall "that simple" ?
s
Some dependencies get inferred, so explicitly calling them out in dependsOn won't change the graph at all. You can add extra dependencies though, this will add a line between the resource and whatever's listed in its dependsOn field as well as help control the order that resources get created in
g
ya i don't use cloud or anything 😛 so would be cli with extra indent. I think i have to dig into my codebase now and see. + also the package i use
s
g
interesting
can i use that with dependsOn?
s
they are two different concepts
so yeah
g
is it under the 
pulumi.ResourceOption
in this case?
oh it's right in the menu of the docs 😛
s
i would follow the advice of Fraser and only use dependsOn if you have an input that isn't expressed as parameter or whatever.. yeah i think all the reousrces have opts param so you would use opts*=ResourceOptions(parent=*parent) etc..
yeah
g
reading is hard
ya i need to dig into the talos package and see what state it returns but i can def. see some stuff is a parent in my case. while also doing 
dependsOn
for example putting a configuration on some specific resource, would be a parent. input wise is stuff coming from the config.
side question, when outputs is 
[secret]
how do i see those?? because i don't have it as a file in my OS. 🤔 (haven't dug into it yet.. i just see it listed as 
secret
)
and i must say, i enjoy pulumi so far.. compared to the terraform i have played with.
❤️ 1
s
You can add the 
--show-secrets
flag to some commands to reveal secrets like this one: `pulumi stack output OUTPUT_NAME --show-secrets`https://www.pulumi.com/docs/iac/cli/commands/pulumi_stack_output/
g
ah
I like what i see now, quite happy. weird though that preview output is different than 
up
🤔 but the 
parent
is doing what i expected.
s
Hmm yea, that is odd. My best guess would be that the Mac values are evaluating to undefined after the program runs and are being omitted from the outputs because of that
e
unknown values will show in outputs, but undefined/null values won't. I think thats the reason for the difference. At preview time "worker 1 Mac" isn't known, after update it ends up resolving to null and so doesn't get output.
g
could be a bug from claude 😛 it is vibe coded.. though i don't really need mac addr printed, but will def look into it.
i think my talos my have the qemu missing s it can't fetch mac addr.
2 Views
Open in Slack
PreviousNext
Powered by