:PROPERTIES:
:ID:       a6c345df-8db9-4538-b87e-0e72e2414905
:END:
#+title: ESP Deployment Pipeline — Index
#+filetags: :ess:microlise:pipelines:index:

* Overview
:PROPERTIES:
:NOTE: This is the master index file. Each heading links to a dedicated notes file.
:END:

The ESP Deployment Pipeline project is an effort to automate the deployment of the ESP application suite (built by ESS) into customer environments using Azure DevOps (AzDO) YAML pipelines and PowerShell scripts.

We are the third team to inherit this work. Team Ludo started it, got the build working in AzDO, and began deployment work before being reassigned. We pick up from there.

* Quick Reference — Key Concepts
| Concept         | What it is                                           | Notes File                           |
|-----------------+------------------------------------------------------+--------------------------------------|
| ESP             | Suite of apps deployed per-customer                  | [[id:091e9bbc-0c9f-43da-81f9-464882c2a15b][ESP Applications]]                     |
| AzDO Pipeline   | YAML-based CI/CD pipeline in Azure DevOps            | [[id:d66e946f-6785-4e8e-ba00-bb25a52237d1][ESP — AzDO Pipeline]]                  |
| PowerShell Arch | Three-tier script architecture (T1/T2/T3)            | [[id:bf63b6c5-f32f-462e-82ad-8d4a15f7ba48][ESP — PowerShell Script Architecture]] |
| Manifest        | Config file defining a customer environment          | [[id:9bf19a8b-5581-4be8-9892-913c51df0128][ESP — The Manifest]]                   |
| Dacpac          | Packaged SQL Server DB schema deployment             | [[id:46add22d-e562-4e3a-a301-d4aea2552952][ESP — Database & Dacpac]]              |
| Stages          | Validate / Prerequisites / Predeploy / Deploy / Post | [[id:cd3cd02f-c9b3-4455-8ce5-b2a5aa458fed][ESP — Deployment Stages]]              |
| Known Issues    | Pain points, risks, and gaps                         | [[id:53d803aa-7e6f-44ed-8d99-a243a5ed5aab][ESP — Known Issues & Risks]]           |
| Open Questions  | Things still TBC or not yet designed                 | [[id:82c3d447-d6d3-498e-9f66-aee60c752462][ESP — Open Questions & TBC Items]]     |
| Glossary        | Terminology reference                                | [[id:2c950d25-6f86-4f83-a7b4-69e2ca2f7023][ESP — Glossary]]                       |

* Context — Why This Project Exists

- Few original ESS engineers remain; those left are on paid customer work
- Manual deployments are slow, risky, and rely on tribal knowledge
- Business goal: /all deployments are consistently repeatable with no manual VM work/
- Initial scope: ROMAC DEV environment only
- Future scope: all environments including PROD and ESS's own data centre

* Team History

| Team      | Contribution                                            | Current Status              |
|-----------+---------------------------------------------------------+-----------------------------|
| ESS       | Built ESP; wrote original deployment docs               | Mostly departed             |
| Team Ludo | Full ESP build in AzDO; started deploy pipeline; dacpac | Reassigned to customer work |
| Our Team  | Inheriting deploy pipeline work                         | Active                      |

* Existing Resources to Review

- Handover from Team Ludo: ~ESP_Pipeline_Handover.docx~
- Ludo deployment docs: ~DEPLOY.md~ (in Repos)
- Ludo deploy scripts: ~deploy~ folder (in Repos)
- ESP Main Build pipeline: AzDO → Pipelines → ~ESS.esp Main Build~
- ESP Deploy Pipeline: AzDO → Pipelines → ~ESS.esp Deploy~

* File Index

| File                                 | Contents                                |
|--------------------------------------+-----------------------------------------|
| [[id:a6c345df-8db9-4538-b87e-0e72e2414905][ESP Deployment Pipeline — Index]]      | This file — master index                |
| [[id:091e9bbc-0c9f-43da-81f9-464882c2a15b][ESP Applications]]                     | ESP app suite breakdown                 |
| [[id:d66e946f-6785-4e8e-ba00-bb25a52237d1][ESP — AzDO Pipeline]]                  | AzDO pipeline structure and concepts    |
| [[id:bf63b6c5-f32f-462e-82ad-8d4a15f7ba48][ESP — PowerShell Script Architecture]] | Three-tier PowerShell architecture      |
| [[id:9bf19a8b-5581-4be8-9892-913c51df0128][ESP — The Manifest]]                   | Manifest design and purpose             |
| [[id:46add22d-e562-4e3a-a301-d4aea2552952][ESP — Database & Dacpac]]              | Database, dacpac, and SQL concerns      |
| [[id:cd3cd02f-c9b3-4455-8ce5-b2a5aa458fed][ESP — Deployment Stages]]              | Stages of deployment — detail per stage |
| [[id:53d803aa-7e6f-44ed-8d99-a243a5ed5aab][ESP — Known Issues & Risks]]           | Known issues and risks                  |
| [[id:53d803aa-7e6f-44ed-8d99-a243a5ed5aab][ESP — Known Issues & Risks]]           | TBC items and open design questions     |
| [[id:2c950d25-6f86-4f83-a7b4-69e2ca2f7023][ESP — Glossary]]                       | Glossary of all technical terms         |
