Elizabeth W
18 lines
1.2 KiB
Markdown
18 lines
1.2 KiB
Markdown
# Implementation Plan: Long-Term Storage Upload
|
|
|
|
## Objective
|
|
Implement an aggregation task that uploads all generated reports from the PVC to long-term storage (e.g., S3/MinIO) for audit trails and historical review.
|
|
|
|
## Requirements
|
|
- Define a task template named `upload-storage`.
|
|
- Depend on the successful completion of **all** parallel scanner tasks (Phase 2).
|
|
- Mount the shared PVC at `/workspace`.
|
|
- Expect S3/MinIO credentials to be injected as environment variables via Infisical (with initContainer wait logic).
|
|
- Use a CLI (like `aws s3 cp` or `mc`) to sync the `/workspace/reports/` directory to a designated bucket, keyed by repository name, date, and commit hash.
|
|
|
|
## Agent Instructions
|
|
1. Add the `upload-storage` template to the `ClusterWorkflowTemplate`.
|
|
2. Configure the DAG dependencies so it waits for all scanners.
|
|
3. Configure the Infisical initContainer to wait for the storage credentials.
|
|
4. **CRITICAL: File Splitting:** Do NOT put everything into one giant file! Split your YAML manifests or configurations into separate, smaller files (e.g. using separate Helm template files, configmaps, or helper scripts) to prevent exhausting the context window.
|