domverse/photoanalyzer
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US08-05 — Automate Container Deployment Acceptance #91

New Issue
Open
opened 2026-08-17 21:11:36 +02:00 by domverse · 0 comments
domverse commented 2026-08-17 21:11:36 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US08-05-container-e2e.md

US08-05 — Automate Container Deployment Acceptance

Epic: E08

As a release owner, I want one automated gate that proves the deployed container, so the
packaged application is verified the same way the host application is.

Acceptance criteria

  • One documented command provisions the composition from the built image against a
    temporary fixture library and an isolated data volume, and destroys it afterwards.
  • A browser journey against the containerized application covers discovery, duplicate
    review, analysis, album proposal, rename, upload preflight, and archive views.
  • An upgrade journey runs the previous published image, then the new one, and asserts
    migrations, journals, jobs, and the thumbnail cache survive.
  • A restart journey kills both containers mid-job and asserts resume without duplicate
    side effects.
  • Security gates run against the deployed instance: unauthenticated access refused,
    forged forwarded headers refused, paths outside the mounted library roots refused, and
    no secret in container logs.
  • Evidence is retained per run and the gate fails on any skipped required check.

Automated tests

  • The container acceptance suite runs on a phase_h marker in CI on main and before a
    published deploy; earlier epic suites keep running unchanged.

Dependencies

  • US08-01 through US08-04
Source specification: [delivery_backlog/stories/US08-05-container-e2e.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US08-05-container-e2e.md) # US08-05 — Automate Container Deployment Acceptance Epic: [E08](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E08-container-deployment.md) As a release owner, I want one automated gate that proves the deployed container, so the packaged application is verified the same way the host application is. ## Acceptance criteria - One documented command provisions the composition from the built image against a temporary fixture library and an isolated data volume, and destroys it afterwards. - A browser journey against the containerized application covers discovery, duplicate review, analysis, album proposal, rename, upload preflight, and archive views. - An upgrade journey runs the previous published image, then the new one, and asserts migrations, journals, jobs, and the thumbnail cache survive. - A restart journey kills both containers mid-job and asserts resume without duplicate side effects. - Security gates run against the deployed instance: unauthenticated access refused, forged forwarded headers refused, paths outside the mounted library roots refused, and no secret in container logs. - Evidence is retained per run and the gate fails on any skipped required check. ## Automated tests - The container acceptance suite runs on a `phase_h` marker in CI on `main` and before a published deploy; earlier epic suites keep running unchanged. ## Dependencies - US08-01 through US08-04
domverse added the type/testarea/testingstatus/backlogpriority/normal labels 2026-08-17 21:11:36 +02:00
domverse added a new dependency 2026-08-17 21:12:20 +02:00
#88 US08-02 — Build a Reproducible Application Image
domverse added a new dependency 2026-08-17 21:12:20 +02:00
#89 US08-03 — Compose the Runtime and Mount the Library Safely
domverse added a new dependency 2026-08-17 21:12:21 +02:00
#90 US08-04 — Publish and Deploy from Gitea Actions
domverse added this to the Photo Analyzer Delivery project 2026-08-17 21:16:47 +02:00
domverse added this to the E08 — Container Deployment milestone 2026-08-17 21:17:43 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label area/testing priority/normal status/backlog type/test
Milestone
No items
No Milestone E08 — Container Deployment
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#87 US08-01 — Make the Trust Boundary Configurable and Authenticated
domverse/photoanalyzer
#88 US08-02 — Build a Reproducible Application Image
domverse/photoanalyzer
#89 US08-03 — Compose the Runtime and Mount the Library Safely
domverse/photoanalyzer
#90 US08-04 — Publish and Deploy from Gitea Actions
domverse/photoanalyzer
Reference: domverse/photoanalyzer#91
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?