Introduce a destroy-only mode in the test runner to run terraform
destroy for the respective cloud provider configurations. This can be
used to destroy cloud resources without going through the whole
provision-test process.
Add a new step in github actions workflow to run the test binary in
destoy-only mode at the very end irrespective of the result of the
previous steps. This ensures that the infrastructure is always
destroyed, even if the CI job is cancelled.
Signed-off-by: Sunny <darkowlzz@protonmail.com>
Explicitly set the test program exit code to 1 when terraform destroy
fails to delete the infrastructure.
This was observed when GKE clusters failed to delete due to delete
protection enabled by default in the latest version of terraform
provider google.
Signed-off-by: Sunny <darkowlzz@protonmail.com>
Add instructions about how to create service accounts with IAM
permissions and populate the secrets and variables required in the CI.
Update the panic recovery code to ensure that the exit status surfaces
on panic along with a log message.
Signed-off-by: Sunny <darkowlzz@protonmail.com>
