The Terraform binary functions as a barrier that definitions must pass through
in order to be instantiated into real infrastructure, and once this happens
successfully the state is stored remotely. This means the state of the
infrastructure can drift in between runs of the Terraform binary's apply
command. In essence, we want to check the current state continuously and take
action to pull the infrastructure back into the desired state. Thus, the name
Gravity.
- Continuous scanning of environmental drift from desired state
- Take action to return to desired state
- Create short-lived clone of the infrastructure based on branch (coming soon)
You can run end-to-end tests using a local Consul cluster for both remote state and as a resource provider. make consul-config to start one running in a container.
Tier 0
- Support workspaces in core server logic
- Cache results in in-memory database
- Add a status UI that reads from cache
Tier 1
- Check that git path and backend path match
- Check that code complies to
terraform fmt - Set warn and enforce mode
Tier 2
- Prometheus metrics
- Slack notifications
- Terragrunt support
- Watch git branches to spin up short-lived infrastructure