101 lines
6.4 KiB
Markdown
101 lines
6.4 KiB
Markdown
# Requirement Verification Questions - andreaslop-site-hosting
|
|
|
|
Source brief: `aidlc-docs/_shared/handoffs/cms-api-foundation-brief-u1-u2.md` (decisions 1-7 in section 2 are taken and NOT re-asked).
|
|
Please fill in your choice after each `[Answer]:` tag.
|
|
|
|
## Question 1: First-administrator setup flow hardening (Security)
|
|
The brief asks us to assess whether the first-admin setup flow on the new instance can be abused by a third party before the first administrator exists (a freshly deployed test host is publicly reachable). What should the scope be?
|
|
|
|
- A) Assess and test the existing Identity behaviour only (no code change in Identity); document the residual risk (anyone who reaches /admin first can claim the admin account)
|
|
- B) Assess, and additionally require a one-time setup token from configuration (env var / appsettings.local.json) on the setup endpoint, only when configured - existing hosts unchanged
|
|
- C) Assess, and restrict the setup endpoint in the new client through configuration only (e.g. host/IP allow-list), no Identity change
|
|
- X) Other (please describe after [Answer]: tag below)
|
|
|
|
[Answer]: B
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Question 2: Commit / PR flow for the two units
|
|
How do we deliver U1 and U2 in git? (Per standing rule: I commit, but never push unless you say so.)
|
|
|
|
- A) One feature branch, commits per unit; no push until you ask; one PR for the whole feature after U2
|
|
- B) One feature branch, but a PR for U1 alone after hand-back (U1 is behaviour-neutral for existing hosts), then U2 on a follow-up branch
|
|
- C) One feature branch, commits per unit; I push and open the PR only when you explicitly say so, timing decided by you per unit
|
|
- X) Other (please describe after [Answer]: tag below)
|
|
|
|
[Answer]: A
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Question 3: Deployment to the test host
|
|
May the CI/CD pipeline deploy the new client to the test host, and how is it triggered?
|
|
|
|
- A) Manual trigger only (workflow_dispatch); I may not run it, you trigger it
|
|
- B) Automatic on merge to master (like the existing pipeline), plus manual trigger
|
|
- C) I only write and verify the workflow (lint/dry run); no deploy to test is performed in this feature, you do the first deploy
|
|
- X) Other (please describe after [Answer]: tag below)
|
|
|
|
[Answer]: X) Pipeline MAY deploy the new client to the TEST host (never production); the CMS session may start the test deploy itself once pipeline and Pi are ready. Bryan: "Hij mag hem uitrollen naar test. Graag zelfs dan kan het zsm getest worden, maar de CI/CD moet er nog op worden ingericht en de host ook."
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Question 4: Test-host prerequisites
|
|
Do the test host and Gitea secrets for Andrea's instance already exist?
|
|
|
|
- A) Yes - host, path, SSH user and Gitea secrets exist; I only need the names (you will tell me, or I read them from the existing workflow)
|
|
- B) Partly - the host exists but secrets/paths for the Andrea instance still have to be defined; I list what is needed in the infrastructure design
|
|
- C) No - nothing exists yet; the design must also cover creating them (documented as manual steps for you)
|
|
- X) Other (please describe after [Answer]: tag below)
|
|
|
|
[Answer]: X) Partly exists (matches B). Bryan: "De host heeft al de juiste accounts om het op te kunnen zetten, maar de inrichting op de host moet nog worden ingeregeld zoals paden, secrets, environment variables." Infrastructure design must list the remaining Pi setup (paths, secrets, env vars, database, reverse proxy) as manual steps for Bryan.
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Question 5: Admin theme scope in U2
|
|
How far should the theme override go beyond colours, radius and font?
|
|
|
|
- A) Tokens only (colours, radius, font) plus logo and favicon, as in the brief; no layout or component changes
|
|
- B) Tokens plus login/setup page branding (logo, title text) via theme assets; no layout changes
|
|
- X) Other (please describe after [Answer]: tag below)
|
|
|
|
[Answer]: A
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Question 6: User Stories stage
|
|
Is a User Stories stage wanted for this infrastructure-heavy feature (personas would be: site visitor, site owner/admin, operator/developer)?
|
|
|
|
- A) Skip User Stories (requirements with acceptance criteria are enough)
|
|
- B) Run a short, minimal User Stories stage
|
|
- X) Other (please describe after [Answer]: tag below)
|
|
|
|
[Answer]: A
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Vraag 7: Beveiligingsextensies
|
|
Moeten de beveiligingsregels (Security Baseline) als harde vereisten worden afgedwongen voor deze feature? (De brief meldt dat je dit al hebt ingeschakeld; graag bevestigen.)
|
|
|
|
- A) Ja - dwing alle BEVEILIGINGSREGELS af als blokkerende vereisten
|
|
- B) Nee - sla alle BEVEILIGINGSREGELS over
|
|
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
|
|
|
|
[Answer]: A
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Vraag 8: Property-based testing
|
|
Moet property-based testing worden afgedwongen? (De brief meldt: gedeeltelijke modus, regels PBT-02, 03, 07, 08, 09; graag bevestigen.)
|
|
|
|
- A) Ja, gedeeltelijk - alleen PBT-02, 03, 07, 08, 09 (puur functies: padresolutie, canonieke vorm, beleid round-trip)
|
|
- B) Ja, volledig - alle PBT-regels als blokkerend
|
|
- C) Nee - sla property-based testing over
|
|
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
|
|
|
|
[Answer]: A
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|
|
|
|
## Vraag 9: Operations-fase
|
|
Moet deze feature na Construction door de Operations-fase (deployment- en monitoringsetup, production readiness)? Let op: de CI/CD-wijzigingen voor U2 zitten sowieso in de requirements; dit gaat om de aparte Operations-fase.
|
|
|
|
- A) Ja - voer de Operations-fase uit na Construction (deployment + monitoring setup)
|
|
- B) Nee - stop na Build and Test (CI/CD voor de testhost wordt wel gebouwd in U2 Code Generation)
|
|
- C) Nog niet zeker - vraag het me opnieuw na de Construction-fase
|
|
- X) Anders (beschrijf hieronder na de [Answer]:-tag)
|
|
|
|
[Answer]: A
|
|
(RELAYED by session 'CMS & API' [343c26] on Bryan's behalf; pending Bryan's confirmation in this session)
|