azaion/gps-denied-onboard

Fork 0

mirror of https://github.com/azaion/gps-denied-onboard.git synced 2026-06-21 08:51:12 +00:00

Files

T

Oleksandr Bezdieniezhnykh 1f634c2604

ci/woodpecker/push/02-build-push Pipeline failed

Details

Update demo replay validation and testing documentation

- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests.
- Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps.
- Updated architectural documentation to include the new demo replay operator flow and its dependencies.
- Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation.
- Added new entries in the dependencies table for upcoming tasks related to the demo replay flow.

These changes improve clarity and usability for operators and developers working with the demo replay system.

2026-06-20 11:24:43 +03:00

2.0 KiB

Raw Blame History

Step 1: Deployment Status & Environment Setup

Role: DevOps / Platform engineer Goal: Assess current deployment readiness, identify all required environment variables, and create .env files. Constraints: Must complete before any other step.

Steps

Read architecture.md, all component specs, and restrictions.md
Assess deployment readiness:
- List all components and their current state (planned / implemented / tested)
- Identify external dependencies (databases, APIs, message queues, cloud services)
- Identify infrastructure prerequisites (container registry, cloud accounts, DNS, SSL certificates)
- Check if any deployment blockers exist
Identify all required environment variables by scanning:
- Component specs for configuration needs
- Database connection requirements
- External API endpoints and credentials
- Feature flags and runtime configuration
- Container registry credentials
- Cloud provider credentials
- Monitoring/logging service endpoints
Generate .env.example in project root with all variables and placeholder values (committed to VCS)
Generate .env in project root with development defaults filled in where safe (git-ignored)
Ensure .gitignore includes .env (but NOT .env.example)
Produce a deployment status report summarizing readiness, blockers, and required setup

Self-verification

All components assessed for deployment readiness
External dependencies catalogued
Infrastructure prerequisites identified
All required environment variables discovered
.env.example created with placeholder values
.env created with safe development defaults
.gitignore updated to exclude .env
Status report written to reports/deploy_status_report.md

Save action

Write reports/deploy_status_report.md using templates/deploy_status_report.md. Create .env and .env.example in project root.

Blocking

BLOCKING: Present status report and environment variables to user. Do NOT proceed until confirmed.

2.0 KiB Raw Blame History