Skip to content

Restructure Functions documentation as top-level concept #15440

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

Merged
merged 2 commits into from
Jul 1, 2025

Conversation

jkodroff
Copy link
Member

Fixes #15438

  • Create new Functions overview page explaining three function types
  • Move provider functions from resources section to functions section
  • Move get functions from resources section to functions section
  • Extract resource methods into separate page
  • Remove JavaScript example from get functions page
  • Update navigation structure and menu weights

🤖 Generated with Claude Code

@pulumi-bot
Copy link
Collaborator

- Create new Functions overview page explaining three function types
- Move provider functions from resources section to functions section
- Move get functions from resources section to functions section
- Extract resource methods into separate page
- Remove JavaScript example from get functions page
- Update navigation structure and menu weights

Addresses GitHub issue #15438 by elevating Functions from a sub-page
of Resources to a top-level concept in the documentation.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@jkodroff jkodroff force-pushed the jkodroff/functions-page-enhancement branch from 0f4c6c5 to 30a1bb5 Compare July 1, 2025 18:17
@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator


## Get functions

**[Get functions](/docs/iac/concepts/functions/get-functions/)** are static functions available on all Pulumi resource types that allow you to reference an existing resource that is not managed by Pulumi. Unlike the `pulumi import` command which brings resources under Pulumi management, get functions simply allow you to read the properties of existing resources.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrasing is a bit language specific. In Go, they are just free-standing functions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Y'know... I did struggle with this. I originally wanted to put the examples of each type in every language, but I could not get the dang invokes to fit on one line.

Added a note for the future: #15457


## Resource methods

**[Resource methods](/docs/iac/concepts/functions/resource-methods/)** are functions attached to specific resource types that return computed values from resources you are managing with Pulumi. These methods are called on resource instances and typically provide additional derived information about that resource.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These functions could also create arbitrary resources. Why do they need to be just computed values.

@jkodroff jkodroff merged commit 69be66f into master Jul 1, 2025
12 checks passed
@jkodroff jkodroff deleted the jkodroff/functions-page-enhancement branch July 1, 2025 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Functions page as a peer of Resources
3 participants