Some of our customers use Jsonnet to generate JSON-based configurations, including Terraform and even Postman collections.
They choose to use it because:
- it allows them to keep things DRY when replicating a configuration artifact across environments
- it is accessible for folks who are not as comfortable with program control flow and other programming constructs. They can start by copying and pasting JSON.
- it provides more advanced control flow and logic features for those who need them
- it provides features for template parameter validation
- it is not that hard to learn
Some things could be improved for sure. Better IDE support, error messages which are not the best. Maybe also a more confident community.
Overall, Jsonnet does seem to hit a pragmatic sweet spot for a bunch of use cases, regardless of the merits of other approaches mentioned in this great discussion!
They choose to use it because:
- it allows them to keep things DRY when replicating a configuration artifact across environments
- it is accessible for folks who are not as comfortable with program control flow and other programming constructs. They can start by copying and pasting JSON.
- it provides more advanced control flow and logic features for those who need them
- it provides features for template parameter validation
- it is not that hard to learn
Some things could be improved for sure. Better IDE support, error messages which are not the best. Maybe also a more confident community.
Overall, Jsonnet does seem to hit a pragmatic sweet spot for a bunch of use cases, regardless of the merits of other approaches mentioned in this great discussion!