Build a new service with checked Terraform and manifests

Cursor assembled a service’s infrastructure files, checked them, and opened a draft pull request for review.

Done with Cursor· Advanced

What they did
They kept a task file in the repo and launched it with the service name and team name. The agent looked for conflicts in GitHub, the cluster, and Terraform state, then generated the Terraform service file, Kubernetes manifests for Deployment, Service, and HPA, and a CI job that ran Trivy. After that, it verified the work with `terraform validate` and a `kubectl` dry run, then created a draft PR with a checklist.
How it went
A new engineer ended up with files that matched the team’s conventions. In another pass, an overly broad cleanup request removed 14 files, including 3 Terraform files still managing state; a checkpoint rollback brought them back.
Tips
Use precise, report-only wording for anything that might delete or trim resources. Keep pull requests small and watch for details, since a reviewer missed a `cpu=10m` limit when they skimmed.

Try it yourself with Cursor

In this repository, use the task file to create a new service for [service name] and [team name]. Start by checking for conflicts in GitHub, the cluster, and Terraform state. Then generate the Terraform service file, Kubernetes Deployment, Service, and HPA, plus a CI job that runs Trivy. Validate the Terraform and do a Kubernetes dry run before you make any changes that could remove, overwrite, or clean up files or resources. Pause and show me a clear list of what will be created, changed, or deleted so I can approve it first. When everything looks right, open a draft pull request with a short review checklist.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on blog.devops.dev ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.