github-mirrors/pi-ape-speckit
1
0
Fork 0
mirror of https://github.com/niels-emmer/pi-ape-speckit.git synced 2026-09-13 23:53:33 +02:00
Code Issues 1 Projects Releases 1 Packages Wiki Activity

[GH-ISSUE #2] [Post-v0.1.0] Prove dev environment with live Azure plan/apply #1

New issue
Open
opened 2026-08-09 19:08:41 +02:00 by zaph0d · 0 comments
zaph0d commented 2026-08-09 19:08:41 +02:00
Owner
Copy link

Originally created by @niels-emmer on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/niels-emmer/pi-ape-speckit/issues/2

Summary

The v0.1.0 release was intentionally published as a starter / baseline scaffold. The main remaining proof gap is a real Azure execution path from the checked-in dev environment root.

Desired outcome

Capture evidence for:

  • successful terraform plan in a real non-prod Azure subscription
  • optional successful terraform apply
  • smoke-check verification of core networking resources
  • Azure Policy baseline assignment evidence

Suggested evidence

  • plan artifact or plan summary
  • screenshots or CLI evidence of created resources
  • policy assignment/compliance snapshot
  • any follow-up defects discovered during the run

Why this matters

This is the main step needed to move from "well-structured starter" toward "Azure-proven baseline".

Originally created by @niels-emmer on GitHub (May 15, 2026). Original GitHub issue: https://github.com/niels-emmer/pi-ape-speckit/issues/2 ## Summary The `v0.1.0` release was intentionally published as a **starter / baseline scaffold**. The main remaining proof gap is a real Azure execution path from the checked-in `dev` environment root. ## Desired outcome Capture evidence for: - successful `terraform plan` in a real non-prod Azure subscription - optional successful `terraform apply` - smoke-check verification of core networking resources - Azure Policy baseline assignment evidence ## Suggested evidence - plan artifact or plan summary - screenshots or CLI evidence of created resources - policy assignment/compliance snapshot - any follow-up defects discovered during the run ## Why this matters This is the main step needed to move from "well-structured starter" toward "Azure-proven baseline".
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.1.0
Labels
Clear labels   
enhancement

   
pull-request
Mirrored from GitHub Pull Request

No labels
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
github-mirrors/pi-ape-speckit#1
No description provided.