Show HN: Precloud – Dynamic tests for infrastructure-as-code (github.com)
Infrastructure as code (IaC) often fails during deployment due to dynamic constraints such as name collisions, quota limits and other resource-specific constraints that devs run halfway into an IaC deployment. We witnessed this first hand at TinyStacks and built precloud - an open-source framework to define and run dynamic tests before IaC deployments.
The precloud framework currently supports Terraform and AWS CDK with several default checks (unique names, service quota checks and more) and ability to define your own!
17 comments
[ 4.1 ms ] story [ 46.1 ms ] threadThat said, if you like infra-as-code and are scaling your usage to more people, I recommend taking a look at tools like Spacelift[0].
We're a CI/CD that's specialized for infra-as-code and integrate very deeply with Terraform, CloudFormation, and similar tools workflows. This way we can give you better visibility, security and easy customizability through automations that are tailor-made for infra-as-code use cases. You can ofc additionally also hook in tools like this one.
Esp. if you want a single team creating reusable templates and guardrails for the whole company, Spacelift can help you a lot, but it's very useful for any bigger group of people using IaC together.
Disclaimer: Software Engineer at Spacelift, grains of salt shall be taken with the above
[0]: https://spacelift.io
The default plugins present are the 6 mentioned here https://github.com/tinystacks/precloud/blob/main/PLUGINS.md. They’re all published on npm and github
[0] https://terrateam.io
I always wonder at the authors motivation to use node when the majority of the ecosystem is written in golang. This is actually one of the main reasons I dont use terraform CDK right now. Why is CDK node first (I know there is golang support) when terraform is all golang?
https://github.com/terraform-linters/tflint-ruleset-aws/blob...
https://github.com/aws-cloudformation/rain/pull/93