Skip to content
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

Suggestions for additional docs for dynamic resources #12151

Open
cnunciato opened this issue Jun 27, 2024 · 0 comments
Open

Suggestions for additional docs for dynamic resources #12151

cnunciato opened this issue Jun 27, 2024 · 0 comments
Labels
area/docs Improvements or additions to documentation

Comments

@cnunciato
Copy link
Contributor

Some feedback from an otherwise happy user:

Dynamic resources are great but it would be great to have a fully featured example closer to the top of the documentation which clearly shows how to access T for Input types (there’s an example at the bottom with LabelInputs and LabelResourceInputs which is helpful but I missed this on first read as it’s so far down and not covered in the section on Inputs).

The outputs on dynamic resources are not type safe. I need to manually declare the public read only properties which will exist at runtime but this is not the best DX. Ideally, there would be a “myCustomResource.outputs” property which is strongly typed using a generic on ResourceProvider.

@github-actions github-actions bot added the needs-triage Needs attention from the triage team label Jun 27, 2024
@github-project-automation github-project-automation bot moved this to 🤔 Triage in Docs 📚 Jun 27, 2024
@sean1588 sean1588 moved this from 🤔 Triage to 🧳 Backlog in Docs 📚 Jul 1, 2024
@sean1588 sean1588 added area/docs Improvements or additions to documentation and removed needs-triage Needs attention from the triage team labels Jul 1, 2024
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
Projects
Status: 🧳 Backlog
Development

No branches or pull requests

2 participants