Replies: 2 comments 2 replies
-
That's the reason we built dagger, it's basically an execution engine behind cue (the execution happens in containers that are generated automatically) - so you attach any execution step (like scripts) anywhere in the cue code and everything is cached automatically and run in parallel (when possible). The dagger terraform library implements what you describe, removes the external step for calling terraform: https://docs.dagger.io/reference/universe/terraform Currently in private beta, soon to be open source publicly. But if you fill in the form, I can give you access right away. |
Beta Was this translation helpful? Give feedback.
-
You could use the 'universe' terraform provider to call cue directly and return the JSON. plug: true |
Beta Was this translation helpful? Give feedback.
-
Is there a terraform provider similar to https://github.com/alxrem/terraform-provider-jsonnet ?
We are using
cue
to generate somejson
configuration that in turn create a grafana dashboard for us. But we want to integrate it withterraform
, so that we only need to specify a couple of parameters that generate templated dashboards.Currently we have an external (to terraform) step that generates the json file, that terraform then references. We want to remove this external step.
Beta Was this translation helpful? Give feedback.
All reactions