MIT License

项目介绍

jonathan-vella/apex 是一个托管在 GitHub 上的开源项目,主要使用 JavaScript 编写,采用 MIT License 许可证,目前获得 219 个 Star、80 次 Fork。

仓库全名
jonathan-vella/apex
开源许可证
MIT License
Star 数
219
Fork 数
80
未关闭 Issue
5

README 摘要

APEX Agentic Platform Engineering eXperience for Azure. APEX is a multi-agent workflow that turns Azure platform engineering requirements into deployable Bicep or Terraform with human approval gates across the lifecycle. Documentation (source) Accelerator template MicroHack Contributing guide Workflow New projects use the practical workflow: reuse captured decisions, batch authorized routine repairs, bound review…

完整内容见 GitHub 原始 README 或本页 。

常见问题

apex 用什么语言开发?

主要使用 JavaScript 编写,采用 MIT License 许可证,目前有 219 个 Star。

apex 可以免费商用吗?

仓库采用 MIT License 许可证,可免费使用与修改,商业使用请遵守许可证条款(例如保留版权声明与许可声明)。

如何获取 apex 的源码?

可以直接克隆仓库:git clone https://github.com/jonathan-vella/apex.git,默认分支为 main;安装与运行步骤见仓库 README。

apex 最近还在维护吗?

仓库最近一次更新为 5 天前,当前有 5 个未关闭 Issue;Star 数为 219,可作为社区活跃度的参考。

关于

GitHub 原始描述(英文)

APEX turns Azure platform engineering requirements into verified, deploy-ready IaC — powered by GitHub Copilot agents, real-time pricing, and built-in compliance.

描述取自 GitHub 官方 API,保持仓库作者书写的原文。

语言占比

Dockerfile
JavaScript
PowerShell
Python
Shell

README

APEX

Agentic Platform Engineering eXperience for Azure.

APEX is a multi-agent workflow that turns Azure platform engineering requirements into deployable Bicep or Terraform with human approval gates across the lifecycle.

Workflow

New projects use the practical workflow: reuse captured decisions, batch authorized routine repairs, bound review closure, and check policy feasibility early. Specialists, production support and the lifecycle approval gates shown below remain. Existing projects retain their legacy contract until explicitly adopted.

%%{init: {'theme':'neutral'}}%% sequenceDiagram autonumber participant U as User participant C as Orchestrator participant R as Requirements participant X as Challenger participant A as Architect participant G as Governance participant IaC as IaC Plan participant Gen as IaC Code participant D as Deploy participant W as As-Built Note over C: ORCHESTRATION LAYER<br/>AI prepares. Humans decide. U->>C: Describe infrastructure intent C->>R: Translate intent into structured requirements R-->>C: 01-requirements.md (includes iac_tool selection) C->>X: Challenge requirements X-->>C: challenge-findings-requirements.json C->>U: Present requirements + challenge findings rect rgba(255, 200, 0, 0.15) Note over U,C: HUMAN APPROVAL GATE U-->>C: Approve requirements end C->>A: Assess architecture (WAF + Cost) Note right of A: cost-estimate-subagent<br/>handles pricing queries A-->>C: 02-architecture-assessment.md + 03-des-cost-estimate.md C->>X: Challenge architecture X-->>C: challenge-findings-architecture.json C->>X: Independently review cost feasibility X-->>C: challenge-findings-cost-estimate.json C->>U: Present architecture + challenge findings rect rgba(255, 200, 0, 0.15) Note over U,C: HUMAN APPROVAL GATE U-->>C: Approve architecture end C->>G: Discover policy constraints G-->>C: 04-governance-constraints.json and Markdown C->>X: Reconcile constraints with approved architecture X-->>C: challenge-findings-governance-constraints-pass1.json C->>U: Review governance constraints and confirmations U-->>C: Approve governance C->>IaC: Create implementation plan using approved inputs Note right of IaC: Unified IaC Planner (05)<br/>routes based on decisions.iac_tool IaC-->>C: 04-implementation-plan.md C->>X: Challenge implementation plan X-->>C: challenge-findings-plan.json C->>U: Present plan + challenge findings rect rgba(255, 200, 0, 0.15) Note over U,C: HUMAN APPROVAL GATE U-->>C: Approve plan end C->>Gen: Generate IaC templates (AVM-first) Note right of Gen: Bicep codegen or Terraform codegen Gen-->>C: infra/bicep/{project} or infra/terraform/{project} rect rgba(0, 150, 255, 0.08) Note over C,Gen: Validation loop alt Validation passes C->>U: Present templates for deployment rect rgba(255, 200, 0, 0.15) Note over U,C: HUMAN APPROVAL GATE U-->>C: Approve for deployment end else Validation fails C->>Gen: Revise with feedback end end C->>D: Execute deployment Note right of D: what-if or terraform plan preview first D-->>C: 06-deployment-summary.md C->>U: Present deployment summary rect rgba(255, 200, 0, 0.15) Note over U,D: HUMAN VERIFICATION U-->>C: Verify deployment end C->>W: Generate workload documentation Note right of W: Reads prior artifacts and deployed resource state W-->>C: 07-*.md documentation suite C->>U: Present as-built docs Note over U,W: AI orchestrated. Human governed. Azure ready.

Assess an Existing Workload

Use /waf-assess-existing with 01-Orchestrator to assess supplied IaC, diagrams, or explicitly scoped read-only Azure evidence. Choose evidence-only (no business interview) or requirements-led assessment. The standalone workflow delivers a WAF report, architecture diagram and cost report after upfront scope authorization and automatic internal work, independent WAF/cost-quality reviews and one final bundle acceptance.

Azure cost reports use authorized actual spend, trends and available forecast; IaC-only uses labelled estimates. The proposed default is last completed calendar month, preceding-month comparison and month-to-date, with current-month forecast when available. Missing evidence and unpriced costs are explicit gaps, not zeros. Acceptance is terminal, not remediation, compliance approval or a handoff to formal Governance/deployment. Existing projects keep their histories and require explicit adoption; the infrastructure delivery workflow is unchanged. New Azure/combined assessments also deliver an Assessment Action Register as Excel plus Markdown. Actions carry evidence, priorities, qualitative effort, relative recommended windows and defensible monthly additions/savings/net change. Unknown costs stay unquantified; overlapping benefits are not summed twice. Edit the structured source and regenerate the snapshot rather than tracking manual Excel changes. IaC-only export is optional; historical runs keep their captured output contract.

Start Here

For new projects, start from the Accelerator template rather than cloning this repository directly:

  1. Create a repository from the Accelerator template.
  2. Open that repository in VS Code and reopen it in the dev container.
  3. Follow the published documentation.

What This Repository Contains

  • Agent definitions, skills, and instruction files for the VS Code Copilot workflow engine
  • Reference implementations for Bicep and Terraform tracks
  • Validation scripts, MCP configuration, and sample agent outputs
  • apex-recall CLI for session state and recall across agent-output/ projects
  • Runtime references, artifact templates, and Architecture Explorer graph metadata

See AGENTS.md for contributor setup, conventions, and validation commands, and CHANGELOG.md for recent changes.

License

MIT. See LICENSE.

评论

暂无评论