-
Notifications
You must be signed in to change notification settings - Fork 0
fix: migrate to Flex Consumption plan with blobContributor role #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,43 +1,9 @@ | ||
| # Roadmap: CAS Reference Product | ||
|
|
||
| ## Phase 1: Public v0.1 Reference Application | ||
| ## Archived Milestones | ||
|
|
||
| **Goal:** Deliver a locally runnable, cloud-ready reference workload without deploying Azure resources. | ||
| - [x] [v0.1 Reference Application](milestones/v0.1-ROADMAP.md) — Delivered a locally runnable, cloud-ready reference workload without deploying Azure resources. | ||
|
|
||
| **Requirements:** API-01, AGENT-01, ID-01, CONTRACT-01, OBS-01, OPS-01, PLAT-01, QUAL-01, DOC-01 | ||
| ## Milestone v0.2 | ||
|
|
||
| **Success criteria:** | ||
| - Local workflow request succeeds and returns canonical events. | ||
| - Tests, lint, type checks, and Docker build pass. | ||
| - Foundry mode uses Next Gen agent references and managed identity. | ||
| - Public documentation states deployment and security boundaries. | ||
|
|
||
| Status: Complete | ||
|
|
||
| ## Phase 2: Telemetry Hardening | ||
|
|
||
| **Goal:** Wire OpenTelemetry end-to-end with lifecycle span events, W3C trace propagation, and Application Insights exporter. | ||
|
|
||
| **Requirements:** TEL-01, TEL-02, TEL-03, TEL-04 | ||
|
|
||
| **Success criteria:** | ||
| - Every /api/v1/workflows request creates a `cas.api.workflows.execute` span with correlation_id, run_id, and intent attributes. | ||
| - Span events `workflow.started`, `workflow.completed`, and `workflow.failed` are emitted at the appropriate lifecycle points. | ||
| - W3C traceparent/tracestate headers on inbound requests are extracted and linked as parent context. | ||
| - Application Insights exporter activates when APPLICATIONINSIGHTS_CONNECTION_STRING is set; no-op otherwise. | ||
| - All telemetry behaviours verified by pytest with InMemorySpanExporter. | ||
|
|
||
| Status: Complete | ||
|
|
||
| ## Phase 3: Docker + CI Publish | ||
|
|
||
| **Goal:** Containerize the app with a production-grade multi-stage Dockerfile and publish the image to GHCR on merge to main. | ||
|
|
||
| **Requirements:** DOCK-01, DOCK-02, DOCK-03 | ||
|
|
||
| **Success criteria:** | ||
| - Multi-stage Dockerfile builds a linux/amd64 image, runs as non-root `appuser`, exposes port 8080, and health-checks via /health/ready. | ||
| - docker-compose.yml starts the local dev stack with env stubs using .env.example. | ||
| - CI docker job builds, smoke-tests (/health/live + /health/ready), and on push to main pushes to ghcr.io/coding-autopilot-system/cas-reference-product. | ||
|
|
||
| Status: Complete | ||
| *To be defined via /gsd-new-milestone* |
File renamed without changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| # Roadmap: CAS Reference Product | ||
|
|
||
| ## Phase 1: Public v0.1 Reference Application | ||
|
|
||
| **Goal:** Deliver a locally runnable, cloud-ready reference workload without deploying Azure resources. | ||
|
|
||
| **Requirements:** API-01, AGENT-01, ID-01, CONTRACT-01, OBS-01, OPS-01, PLAT-01, QUAL-01, DOC-01 | ||
|
|
||
| **Success criteria:** | ||
| - Local workflow request succeeds and returns canonical events. | ||
| - Tests, lint, type checks, and Docker build pass. | ||
| - Foundry mode uses Next Gen agent references and managed identity. | ||
| - Public documentation states deployment and security boundaries. | ||
|
|
||
| Status: Complete | ||
|
|
||
| ## Phase 2: Telemetry Hardening | ||
|
|
||
| **Goal:** Wire OpenTelemetry end-to-end with lifecycle span events, W3C trace propagation, and Application Insights exporter. | ||
|
|
||
| **Requirements:** TEL-01, TEL-02, TEL-03, TEL-04 | ||
|
|
||
| **Success criteria:** | ||
| - Every /api/v1/workflows request creates a `cas.api.workflows.execute` span with correlation_id, run_id, and intent attributes. | ||
| - Span events `workflow.started`, `workflow.completed`, and `workflow.failed` are emitted at the appropriate lifecycle points. | ||
| - W3C traceparent/tracestate headers on inbound requests are extracted and linked as parent context. | ||
| - Application Insights exporter activates when APPLICATIONINSIGHTS_CONNECTION_STRING is set; no-op otherwise. | ||
| - All telemetry behaviours verified by pytest with InMemorySpanExporter. | ||
|
|
||
| Status: Complete | ||
|
|
||
| ## Phase 3: Docker + CI Publish | ||
|
|
||
| **Goal:** Containerize the app with a production-grade multi-stage Dockerfile and publish the image to GHCR on merge to main. | ||
|
|
||
| **Requirements:** DOCK-01, DOCK-02, DOCK-03 | ||
|
|
||
| **Success criteria:** | ||
| - Multi-stage Dockerfile builds a linux/amd64 image, runs as non-root `appuser`, exposes port 8080, and health-checks via /health/ready. | ||
| - docker-compose.yml starts the local dev stack with env stubs using .env.example. | ||
| - CI docker job builds, smoke-tests (/health/live + /health/ready), and on push to main pushes to ghcr.io/coding-autopilot-system/cas-reference-product. | ||
|
|
||
| Status: Complete |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this Flex Consumption template is deployed, the new
functionAppConfigonly defines the code package container; the app settings still never define the requiredAzureWebJobsStorage/AzureWebJobsStorage__*host-storage connection. Because the storage account disables shared-key access, the Functions host has neither a connection string nor an identity-based host storage configuration, so the deployed function app won't be able to start reliably or serve the ingress function after rollout. Add the host storage app setting(s) and the matching storage RBAC for that connection.Useful? React with 👍 / 👎.