late-balloon-24601
12/24/2024, 4:27 PMResourceTransform
appears to give programs a lot less ability to introspect resources compared to the deprecated ResourceTransformation
. For example, the old ResourceTransformation
gives you the instantiated resource directly, so I'm able to walk up the resource tree to get to the parent, allowing me to add a tag to the child resource with metadata about the parent. In comparison, ResourceTransform
doesn't give any info about the parent nor let me take advantage of any of the clever class-related shenanigans I can do with TS/JS, which is sorta the draw for Pulumi for me.
I'm nervous to continue using ResourceTransformation
despite it being way better for my use-case because of the scary deprecation warnings. I understand that transforms
receives something much closer to what the engine itself sees which is nice in some cases, but it kills a lot of the flexibility imo. Is there actually any chance of Transformations
going away any time soon?
I guess it's probably possible to abuse pulumi.runtime
commands to get the actual resource and re-enable that behaviour, but I don't particularly want to go down that route yet...No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by