# 15. Final Thoughts

### Developer Workflow & Automation

1. Write/update code
2. Run changes locally (for dev env)
3. Create pull request
4. Run Tests via CI
5. Deploy to staging via CD (on merge to main)
6. Deploy to prod via CD (on release)

***

### Additional Tools

1. Terragrunt
   * Minmizes code repitition
   * Enables multi-account seperation (improved isolation/security)
2. Cloud Nuke
   * Easy cleanup of cloud resources
3. Makefiles
   * Prevent human erro

***

### Potential Gotchas

* Name changes when refactoring
* Sensitive data in Terraform state files
* Cloud timeouts
* Naming conflicts
* Forgetting to destory test-infra
* Uni-directional version upgrades
* Multiple ways to accomplish same config
* Some params are immutable
* Out of band changes

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://notes.nomanaziz.me/devops/infrastructure-as-a-code-iac/terraform/15.-final-thoughts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.