-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changes to docs for 0.3, first draft #447
Conversation
lbialy
commented
Apr 10, 2024
- better explanation of resource constructor syntax
- better explanation of Output/Input dynamics, how they work
- draft of explanation of how to structure besom programs, I think we should expand upon this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, got one suggestion.
website/docs/async.md
Outdated
</TabItem> | ||
</Tabs> | ||
|
||
There is a way to inform Pulumi engine that some of the resources have to be created, updated or deleted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be worth noting that "depends on" is needed only when Pulumi cannot infer the sequence from output dependency graph
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, this is exactly what I had in mind here:
draft of explanation of how to structure besom programs, I think we should expand upon this
but it feels like a big topic and I'm thinking about a best practices section to distill what happens if you do stuff what way there and explain it a bit more
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd add a word explicitly before inform.
And add a short remark that Pulumi tries to infer sequence from dependency graph.
67b1de4
to
a8bf7e3
Compare
* changes to docs for 0.3.x * updated changelog for 0.3.0