-
Notifications
You must be signed in to change notification settings - Fork 210
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
Transformation Resource Option Page Doesn't Provide a Complete Example #11652
Open
Tracked by
#11197
Labels
area/docs
Improvements or additions to documentation
kind/enhancement
Improvements or new features
size/S
Estimated effort to complete (1-2 days).
Comments
@RobbieMcKinstry im going to remove the needs triage label on this, if yall would like this content updated, someone from the platform team is more than likely going to need to open a pr. id be happy to review or help however i can. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/docs
Improvements or additions to documentation
kind/enhancement
Improvements or new features
size/S
Estimated effort to complete (1-2 days).
What happened?
While triaging a user-reported issue today, I came across the Transformation resource option page. I noticed this page doesn't contain a complete example, only a snippet.
Specifically, the example shows code for a component resource named
MyVpcComponent
. However, it doesn't provide the definition ofMyVpcComponent
. This opens up the possibility for confusion; users might not understand what they have to do with the component options. For example, you could implementMyVpcComponent
incorrectly as follows:Steps to reproduce
Expected Behavior
I expected all identifiers in the example program to be defined.
Actual Behavior
MyVpcComponent
is undefined.Output of
pulumi about
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: