PyTerraBackTyl
PyTerraBackTyl copied to clipboard
dev-dull
PyTerraBackTYL is a generic Terraform HTTP backend for managing your Terraform lock states, and terraform.tfstate file. Allows for additional post-processing of the lock and state information to allow...
Once a new strategy for integration testing has been developed (see #56), test all the backends provided in the project. Initial proposal would be to add a second variable to...
Currently, the CI has a number of steps in CI that perform some lightweight integration tests which all report to `GITHUB_STEP_SUMMARY` on success. This strategy should be retooled so that...
Test if PyTerraBackTYL is compatible with [OpenTofu](https://opentofu.org/).
After verifying compatibility, or updating PyTerraBackTYL to be compatible with OpenTofu (see Issue #54), update CI to include a second `matrix` that validates against commonly used versions of OpenTofu. https://github.com/dev-dull/PyTerraBackTyl/blob/3f2e78138f356eb31e83c51e254c048fe8c3da45/.github/workflows/docker-build.yaml#L65C1-L65C30
CI uses a mix of `GITHUB_ENV` and `GITHUB_OUTPUT`. The use of `GITHUB_ENV` is leftover from initial development. It should be possible to consolidate on `GITHUB_OUTPUT`. https://github.com/dev-dull/PyTerraBackTyl/blob/3f2e78138f356eb31e83c51e254c048fe8c3da45/.github/workflows/docker-build.yaml#L25
Unless you squint at the error message, a misconfigured backend can result in a misleading `KeyError: 'backend'` error message. ``` 2025-10-13 08:07:51,886 - PyTerraBackTyl - ERROR - Exception on /...
The docker image for PyTerraBackTYL currently invokes the service using Python/Flask directly. Since it is intended to be ran as an internally facing service, it is "probably fine" however, using...
PyTerraBackTYL has now had two cases where the Git based backend has had the potential of introducing unnecessary risk into the system. Additionally, **_Git is fundamentally the wrong place to...
Create a new backend that saves the Terraform state into Hashicorp Vault.
While investigating #58, the unfortunate discovery of #59 was made. This ticket is to include functionality testing (integration testing) of *ALL* included backends before a new container image is shipped...