Skip to content

Commit cc287fe

Browse files
alliscodeBen ThomasCopilotPrototype Author
authored
feat(infrastructure): add protected Azure deployment (#302)
## Why Operators need a protected, repeatable way to update the named non-production Azure Hub installation without passing application secret values through GitHub Actions or bypassing the existing serialized release procedure. ## What changes This adds a manual `hub-azure-development` deployment workflow with GitHub Environment approval, Azure OIDC authentication, non-cancelling deployment concurrency, and immutable image publication from the exact checked-out commit. The workflow reconstructs private Terraform inputs from protected non-secret coordinates and Key Vault references, then uses the existing maintenance-window release command. It preserves separate deployment, Hub, setup, and provisioning identities; the release identity manages state, ACR publication, resource configuration, references, and RBAC without Key Vault secret-data access. The Azure contracts now support routine releases without receiving the PostgreSQL administrator password, preserve the existing deployment storage grant, and verify setup success, the active image digest, readiness, health, and configured authentication providers before releasing the deployment lease. Operator documentation covers Environment variables, federated credentials, least-privilege RBAC, public runtime settings, Key Vault references, recovery, and current limitations. A real non-production Azure exercise is still required to verify OIDC federation, RBAC propagation, ACR publication, Key Vault resolution, private PostgreSQL connectivity, and Container Apps rollout. GitHub setup status also requires a Hub administrator session, so that remains a separate authenticated operator smoke test. --------- Co-authored-by: Ben Thomas <bentho@Bens-MacBook-Pro.local> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Prototype Author <author@example.com>
1 parent 39657ad commit cc287fe

16 files changed

Lines changed: 1335 additions & 36 deletions

File tree

‎.github/workflows/hub-azure-deploy.yml‎

Lines changed: 424 additions & 0 deletions
Large diffs are not rendered by default.

‎AGENTS.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Follow the [commit and PR conventions](CONTRIBUTING.md#commits-and-pull-requests
3434
- `actions/build/` owns the artifact contract between prototype repositories and Hub.
3535
- `packages/learning/` owns the learning contracts, the memory provider and consolidator interfaces, the reference providers and consolidators, the conformance suite, and the `replica-learning` command. It is private repository source with no release yet. Read its `README.md` and [ADR 0001](docs/adr/0001-learning-extension-architecture.md) before changing it.
3636

37-
The new Hub has no release or deployment workflow. The starter follows `main` and has no separate release process. Start a new agent session after copying the starter so its local skills are discovered.
37+
The new Hub has one protected manual workflow for a named non-production Azure installation. It does not publish prototypes or provide a general release service. The starter follows `main` and has no separate release process. Start a new agent session after copying the starter so its local skills are discovered.
3838

3939
For requests to create a prototype repository or set up an existing repository for prototyping, read [prototype repository setup](docs/prototype-repository-setup.md) before acting. It owns target selection, starter installation, the fresh-session handoff, and the path from local preview to optional guidance, a team baseline, or Hub.
4040

‎docs/prototype-repository-setup.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ This milestone checks the existing starter page without building product UI. Rep
6969
| Product or design-system setup | Run the new repository's `/setup-skills` with the supplied sources. Reuse prior answers. Follow its source intake, installation approval, draft review, and separate activation steps. |
7070
| Reference-based starting UI | Complete the applicable guidance setup, then use the local `create-prototype` skill to build the requested shell or page. Establish whether components come from an installable package, permitted source reuse, or newly authored components. Verify the rendered result against the authorized reference. |
7171
| Shared team baseline | Complete the applicable guidance setup, [prepare useful starting pages](prototype-environment.md#3-prepare-useful-starting-pages), and review them together. Then [share the baseline on GitHub](#share-the-baseline-on-github). |
72-
| Hosted publishing and comments | Explain that the new Hub cannot publish prototypes or accept comments yet, and has no deployment workflow. Do not infer setup steps from old releases. Local previews and a shared repository remain available. |
72+
| Hosted publishing and comments | Explain that the new Hub cannot publish prototypes or accept comments yet. Its protected Azure installation workflow does not add these product features. Do not infer setup steps from old releases. Local previews and a shared repository remain available. |
7373

7474
Guidance drafts are not active guidance. Installed tokens or packages are not proof that reference components are usable or that a shell resembles the reference. Keep those outcomes distinct.
7575

‎docs/testing-and-review.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ When a command gains a dependency or build prerequisite, update its local setup
5050

5151
All CI workflows run on every pull request and push to `main`. Do not skip checks based on changed paths or add jobs that only combine other jobs' results. Configure branch protection to require the individual checks.
5252

53-
Hub reports lint, types, unit tests, database tests, the frontend/API build, Storybook, and Controls/extension checks separately. Only the database test command starts PostgreSQL. The new Hub has no production-image or release jobs.
53+
Hub reports lint, types, unit tests, database tests, the frontend/API build, Storybook, and Controls/extension checks separately. Only the database test command starts PostgreSQL. Image smoke testing remains independent CI; the protected Azure release workflow is manual and is not a required pull request or push check.
5454

5555
Maintainers must update branch rules when required checks change. Editing a workflow does not update those rules.
5656

‎hub/docs/deployment.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,6 @@ The deployment orchestrator owns serialization of the complete release, includin
7272

7373
CI checks the image against disposable PostgreSQL, including setup, frontend/API serving, readiness, and termination. Set `NPM_REGISTRY` when running `node hub/script/check-image/index.ts` locally if the build requires a proxy. This is not a supported local-production installation. The existing devcontainer remains the development environment.
7474

75-
The [Azure reference installation](../../infrastructure/README.md) uses Terraform and a serialized maintenance-window release. It supplies GitHub identifiers and Key Vault-backed credential references; configure the exact Container Apps proxy-chain length before enabling authentication.
75+
The [Azure reference installation](../../infrastructure/README.md) uses Terraform and a serialized maintenance-window release. Its protected GitHub Actions workflow builds the reviewed commit and updates one non-production installation through OIDC without receiving application secret values. It supplies public GitHub identifiers directly and credential references through Key Vault; configure the exact Container Apps proxy-chain length before enabling authentication.
7676

7777
An actual cloud deployment must additionally verify credentials, networking, data survival, backup and restore, domain configuration, and release ordering in an authorized environment. Never commit secrets, tenant-specific parameter files, or generated service addresses.

0 commit comments

Comments
 (0)