Skip to content

vibe_coding.md

Latest commit

 

History

History
71 lines (44 loc) · 3.16 KB

vibe_coding.md

File metadata and controls

71 lines (44 loc) · 3.16 KB

Vibe Coding Guide

It is possible to vibe code new terraform examples in this repo! The recommended approach is to follow the plan-implement-apply pattern. This starts with running /1-plan YOUR_IAC_REQUIREMENTS in GitHub Copilot Chat.

If you want to go straight to the prompts, check out the files in the .github/ folder.

Vibe Coding Walkthrough: Plan-Implement-Apply

We started with project by building the foundations for the "plan-implement-run" pattern. The only difference is that instead of running an app, we are applying a Terraform template. Check out this blog post to learn of its foundations.

Agent and Model Recommendations

Most of the modules here were implemented using the following:

  • Terraform MCP Server
  • Azure MCP Server

This is simplified through the aztf-agent chatmode. We also used Claude Sonnet 3.5/3.7/4 for most of the implementations. Feel free to experiment with other models.

Step 1: Plan

Open up GitHub Copilot Chat and run one of the following:

/1-plan TERRAFORM_MODULE

for example,

/1-plan dev_center_project_environment_type

This will generate a new plan in /docs/plans/. Review the generated plan and keep iterating with the agent on what needs to be revised. See demo video.

Tip

To see previously generated plans, check out the /docs/plans/ folder.

Step 2: Implement

/2-implement #file:THE_GENERATED_PLAN.plan.md

This will begin the implementation process based on the plan. See demo video.

Tip

If you are able, it is useful to actively read and check what the agent is doing. If you see that it is going the wrong direction, press the STOP button in the Copilot Chat panel and correct its course.

The agent will stop implementation at some point, ask it to continue As the agent goes through the implementation plan, it will occassionally "summarize the conversation history". This means that the agent's context window is full and it will try to summarize everything in the previous chat history.

UNFORTUNATELY this also means that some of the clear instructions in our /2-implement prompt was summarized, causing it to stop instead of continuing (that's my theory at least).

Step 3: Apply

Once implementation is done, it's time to test deploying the Terraform template to an Azure environment. Most of the issues are usually found and fixed in this step. But you will need the following before proceeding:

  1. An active Azure subscription
  2. The necessary RBAC permissions to the Azure subscription (Owner or Contributor)

Once ready, run:

/3-apply #file:THE_GENERATED_PLAN.plan.md

This will run terraform apply and fix the issues encountered. This step usually takes time (as running terraform plan, apply and destroy takes time). Watch the chat window actively and intervene if necessary. See demo video.

Once finished, you are done! Commit and push the changes and repeat for other template implementations.