If you haven't already, generate a new Runiac project using the starter:
Run a local deployment in the newly created
step1/default/main.tf and start adding resources. Once ready to test run the same
runiac deploy command.
Finally, You can clean up any resources that were created by runiac with the
Congratulations! You've successfully run, modified and destroyed your Runiac project.
Be aware that some Google Cloud Platform resources are not deleted immediately. Common examples include IAM roles, among others, which remain in the system for a period of time before finally being purged (ie: soft deletes). The Terraform provider documentation will usually call this out in a warning.
This has implications on ephemeral deployments; you cannot create a role with a given name, run runiac with the
--self-destroy flag in this example, and rerun runiac immediately afterwards. GCP will detect a conflict when the same role is created again, and as a result, your deployment will fail.
For these types of resources, the recommendation is to only deploy them to non-ephemeral environments. You can leverage Terraform's
count property and runiac's
namespace variable to conditionally deploy such resources: