This commit is contained in:
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- api
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
**Z notes on API management so I don’t forget**
|
||||
|
||||
1. API stands for application programming interface. It allows systems to communicate with each other.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What is ESP?
|
||||
|
||||
ESP is a software suite built by ESS and sold to customers. It is deployed on a **per-customer basis** — similar to TMC (another internal product) but with fewer applications in the suite.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- ess
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# The ESP Database
|
||||
|
||||
ESP uses a single SQL Server database called **EspBroker**. This is deployed and upgraded as part of the overall ESP deployment process.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
The deployment is broken into **discrete stages** that can be run in any combination. This allows you to, for example, only run validation, or only run post-deploy checks, without triggering a full deployment.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
Reference glossary for all technical and project-specific terms used across the ESP deployment pipeline project. Alphabetically ordered.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
This file documents all known issues, risks, and blockers identified in the handover material. Understanding these early will help you avoid surprises.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What Is the Manifest?
|
||||
|
||||
The manifest is a **configuration file** that describes a specific customer environment. The deployment scripts read the manifest to understand **what** to deploy, **where**, and **how**.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
These are items explicitly marked as TBC or not yet designed in the handover material. They represent real blockers or gaps that need to be resolved before the pipeline is complete. Use this file to track answers as they are determined.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# What is Azure DevOps (AzDO)?
|
||||
|
||||
Azure DevOps is Microsoft's platform for DevOps workflows. It covers:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
The deployment scripts are structured in **three tiers**, loosely analogous to a presentation/domain/data layered architecture in software. This separation exists to:
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
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.
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- ess
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
Joined team Shackleton on \<2026-04-07 Tue\>, who are now overseeing the deployment process for ESS applications.
|
||||
|
||||
[[ESS ESP Index]]
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- microlise
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
1. What are you most proud of doing in the last 2 years?
|
||||
|
||||
2. What do you think you could have done better in the last two years?
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- microlise
|
||||
- moc
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# \<2026-05-27 Wed\>: XSS ROM Work
|
||||
|
||||
## [[Session Stored XSS PENTEST]]
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Clothing
|
||||
|
||||
# Bag(s)
|
||||
|
||||
@@ -1,3 +1,10 @@
|
||||
---
|
||||
note type:
|
||||
- microlise
|
||||
- note
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Overview
|
||||
|
||||
DBAs are seeing high CPU and memory usage on SQL production servers due to SEB
|
||||
|
||||
@@ -1,3 +1,11 @@
|
||||
---
|
||||
note type:
|
||||
- note
|
||||
- microlise
|
||||
- security
|
||||
date: 2026-06-03
|
||||
done: true
|
||||
---
|
||||
# Links:
|
||||
|
||||
- [[Cross Site Scripting (XSS)]]
|
||||
|
||||
Reference in New Issue
Block a user