Skip to content

We should add a new document to cover the workshop outcomes. Guidance from operator: Try again the server dropped. - #6

Merged
owainow merged 4 commits into
mainfrom
run/run-2026082514030770
Aug 25, 2026
Merged

owainow merged 4 commits into
mainfrom
run/run-2026082514030770

Conversation

@owainow

@owainow owainow commented Aug 25, 2026

Copy link
Copy Markdown
Owner

Run run-2026082514030770 — artifacts:

implement

Denied by policy "confirm_run_command". ("denied by pre-tool hook: Denied by policy "confirm_run_command".")OUTCOMES.md has been implemented in the repository root according to adlc/specify.md and adlc/plan.md.

Summary of Completed Sections

  1. Executive Summary & Workshop Overview:
    • Outlines the Jamstack architecture, modern serverless application topology, and zero-code CRUD API layer on Azure.
  2. Architectural Stack & Technology Matrix:
    • Comprehensive matrix covering Vue.js, Azure Static Web Apps, Azure SQL Database, Data API builder (swa-db-connections/staticwebapp.database.config.json), Easy Auth with GitHub IDP, Azure Functions, and GitHub Actions CI/CD.
  3. Detailed Module Learning Outcomes:
    • Full-Stack Serverless: Jamstack paradigm and eliminating boilerplate CRUD code via DAB.
    • Infrastructure & Provisioning: Azure CLI commands for SWA and Azure SQL, firewall rules (AllowAllWindowsAzureIps), Entra ID admin setup, and least-privilege runtime user (todo_dab_user).
    • Automated CI/CD & Preview Environments: 6 GitHub repository secrets (AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, SUBSCRIPTION_ID, AZURE_STATIC_WEB_APPS_API_TOKEN, `AZURE_SQL_CONNECTION_ST

plan

Implementation Plan: Workshop Learning Outcomes & Deliverables Documentation

1. Executive Summary & Objective

This implementation plan defines the complete specification and structural blueprint for generating OUTCOMES.md at 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 on README.md and adlc/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| SQL
Loading

3. Resolution of Findings & Key Enhancements

  1. In-Progress Deliverables Specification:
    • Explicitly detail the database schema evolution in database/TodoDB/Tables/dbo.todos.sql introducing the `[inprogress] B

specify

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.md contains 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

  • Target File: OUTCOMES.md (root directory)
  • Primary Heading: # Cardiff Serverless Days Workshop: Learning Outcomes & Deliverables

4. Key Requirements & Content Specifications

4.1 Target Audience & Workshop Overview

  • Clear statement of workshop goals and architectural stack:
    • Frontend: Vue.js Single Page Application (SPA) with Vite.
    • Hosting & CI/CD: Azure Static Web Apps (SWA) and GitHub Actions.
    • Data Layer & API Engine: Azure SQL Database integrated with Azure Static Web Apps Database Connections powered by Data API builder (DAB) exposing REST and GraphQL endpoints.
    • Identity & Security: Easy Auth configured with GitHub Identity Provider (IDP) and DAB role-based authorization policies (anonymous vs authenticated).
    • Serverless API Extensibility: Managed Azure Functions HTTP endpoints

tasks

Tasks: Workshop Learning Outcomes & Deliverables Documentation

This task list guides the implementation of OUTCOMES.md in the repository root according to adlc/specify.md and adlc/plan.md.


Task 1: Create Document Foundation & Architecture Matrix

  • Create OUTCOMES.md in the repository root.
  • Set exact level 1 heading: # Cardiff Serverless Days Workshop: Learning Outcomes & Deliverables.
  • Author Section 1: Executive Summary & Workshop Overview explaining the workshop goals, full-stack Jamstack paradigm, and serverless application topology.
  • Author Section 2: Architectural Stack & Technology Matrix featuring a table mapping:
    • Frontend: Vue.js SPA with Vite.
    • Hosting & Platform: Azure Static Web Apps (SWA).
    • Data Layer: Azure SQL Database (TodoDB).
    • API Engine: Data API builder (DAB) / SWA Database Connections (swa-db-connections/staticwebapp.database.config.json).
    • Identity & Access: Easy Auth with GitHub IDP & DAB role-based authorization policies.
    • Serverless API Extensibility: Managed Azure Functions HTTP en

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
@owainow
owainow merged commit b4f6dff into main Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant