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.

Sign up for GitHub

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

Jump to bottom

Explore automapping for resource marshaling #445

Open
guineveresaenger opened this issue Dec 12, 2022 · 1 comment
Open

Explore automapping for resource marshaling #445

guineveresaenger opened this issue Dec 12, 2022 · 1 comment
Labels
impact/reliability Something that feels unreliable or flaky kind/engineering Work that is not visible to an external user

Comments

@guineveresaenger
Copy link
Contributor

guineveresaenger commented Dec 12, 2022 •
edited
Loading

Resource marshalling is manually implemented. While there's unit tests, it would be great if we could instead automap resource inputs into Go structs, and there is a bit of tooling that could be leveraged.

Prior art: #435
Related: #439
@guineveresaenger guineveresaenger added impact/reliability Something that feels unreliable or flaky kind/engineering Work that is not visible to an external user labels Dec 12, 2022
@t0yv0
Copy link
Member

t0yv0 commented Feb 13, 2023

Really would love to see pulumi/pulumi#11530 addressed first, then it would be nice and easy to back port it to pulumi-docker here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
impact/reliability Something that feels unreliable or flaky kind/engineering Work that is not visible to an external user
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@t0yv0 @guineveresaenger