Repository navigation
We should add a new document to cover the workshop outcomes. Guidance from operator: Try again the server dropped. - #6
Merged
Conversation
Run-Id: run-2026082514030770 Phase: specify Agent-Id: planner-1
Run-Id: run-2026082514030770 Phase: plan Agent-Id: planner-1
Run-Id: run-2026082514030770 Phase: tasks Agent-Id: planner-1
Run-Id: run-2026082514030770 Phase: implement Agent-Id: implementer-1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Run
run-2026082514030770— artifacts:implement
Denied by policy "confirm_run_command". ("denied by pre-tool hook: Denied by policy "confirm_run_command".")
OUTCOMES.mdhas been implemented in the repository root according toadlc/specify.mdandadlc/plan.md.Summary of Completed Sections
swa-db-connections/staticwebapp.database.config.json), Easy Auth with GitHub IDP, Azure Functions, and GitHub Actions CI/CD.AllowAllWindowsAzureIps), Entra ID admin setup, and least-privilege runtime user (todo_dab_user).AZURE_CLIENT_ID,AZURE_CLIENT_SECRET,AZURE_TENANT_ID,SUBSCRIPTION_ID,AZURE_STATIC_WEB_APPS_API_TOKEN, `AZURE_SQL_CONNECTION_STplan
Implementation Plan: Workshop Learning Outcomes & Deliverables Documentation
1. Executive Summary & Objective
This implementation plan defines the complete specification and structural blueprint for generating
OUTCOMES.mdat the repository root. The document synthesizes the learning outcomes, technical proficiencies gained, architectural patterns, and verifiable deliverables produced throughout the Cardiff Serverless Days Azure Workshop based onREADME.mdandadlc/specify.md.2. Architectural Overview
graph TD Client["Client: Vue.js SPA (Vite)"] Auth["Easy Auth (GitHub IDP)"] SWA["Azure Static Web Apps (SWA)"] DAB["Data API builder (DAB) / SWA Database Connection"] AppUser["Least-Privilege User: todo_dab_user"] SQL[("Azure SQL Database: TodoDB")] Functions["Azure Functions (/api/helloworld & BYOF)"] CICD["GitHub Actions (Multi-Branch CI/CD)"] Client -->|HTTPS / REST / GraphQL| SWA SWA -->|GitHub OAuth| Auth SWA -->|DAB Engine| DAB DAB -->|Connects via todo_dab_user| SQL SWA -->|Proxies /api| Functions CICD -->|Deploy Preview / Prod| SWA CICD -->|DACPAC Deployment DDL Admin| SQL3. Resolution of Findings & Key Enhancements
database/TodoDB/Tables/dbo.todos.sqlintroducing the `[inprogress] Bspecify
Specification: Workshop Learning Outcomes & Deliverables Documentation
1. Objective
Add a dedicated documentation file,
OUTCOMES.md, to the repository root that outlines the learning outcomes, technical proficiencies gained, and concrete deliverables produced by completing the Cardiff Serverless Days Azure Workshop.2. Background & Motivation
The workshop repository guides attendees through building, deploying, and extending a full-stack serverless Todo application using Azure Static Web Apps (SWA), Azure SQL Database, Data API builder (DAB), and Azure Functions. While
README.mdcontains step-by-step technical instructions, there is currently no standalone document summarizing the structured learning outcomes, architectural tracks, or concrete deliverable verification checklist for attendees.3. Scope & Target File
OUTCOMES.md(root directory)# Cardiff Serverless Days Workshop: Learning Outcomes & Deliverables4. Key Requirements & Content Specifications
4.1 Target Audience & Workshop Overview
anonymousvsauthenticated).tasks
Tasks: Workshop Learning Outcomes & Deliverables Documentation
This task list guides the implementation of
OUTCOMES.mdin the repository root according toadlc/specify.mdandadlc/plan.md.Task 1: Create Document Foundation & Architecture Matrix
OUTCOMES.mdin the repository root.# Cardiff Serverless Days Workshop: Learning Outcomes & Deliverables.TodoDB).swa-db-connections/staticwebapp.database.config.json).