You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe you’ve already considered this — if so, feel free to ignore 🙂
I was wondering whether Terratest could leverage Terraform provider schemas in a way similar to what Pulumi does with the pulumi-terraform-bridge / tfgen pipeline.
pulumi package add terraform-provider
generates typed models from provider schemas, which makes assertions much easier than working with map[string]any.
In Terratest today, the options are either:
• prebuilt helpers in modules/* (which need ongoing maintenance), or
• terraform.OutputStruct, which still requires manually defining structs that must stay in sync with outputs.
Curious if this aligns with your long-term direction or if something like this has already been ruled out. I'd be happy to collaborate if the idea makes sense to you^^
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Maybe you’ve already considered this — if so, feel free to ignore 🙂
I was wondering whether Terratest could leverage Terraform provider schemas in a way similar to what Pulumi does with the pulumi-terraform-bridge / tfgen pipeline.
generates typed models from provider schemas, which makes assertions much easier than working with map[string]any.
In Terratest today, the options are either:
• prebuilt helpers in modules/* (which need ongoing maintenance), or
• terraform.OutputStruct, which still requires manually defining structs that must stay in sync with outputs.
Curious if this aligns with your long-term direction or if something like this has already been ruled out. I'd be happy to collaborate if the idea makes sense to you^^
All reactions