Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
1.4 KiB
1.4 KiB
S3 Deployment
Background
We have a storage provider abstraction that is used to abstract away how we handle file storage for the document system, etc. It has a factory that is used to properly instantiate the correct class, specified via configuration, etc.
Alga PSA base folder: alga-psa.worktrees/s3-fileprovider-deployment NM Kube Config base folder: nm-kube-config/
s3: server/src/empty/lib/storage/providers/S3StorageProvider.ts file: server/src/lib/storage/providers/LocalStorageProvider.ts
base provider: server/src/lib/storage/providers/StorageProvider.ts configuration info: server/src/config/storage.ts
Task at hand
- Ensure file system configuration can happen via env vars
- Ensure that we can specify the s3 provider
- Ensure that s3 provider can be configured for our helm chart (located at helm/)
- Ensure that the hosted.values.yaml configuration has a configuration for s3
- nm-kube-config/alga-psa/hosted.values.yaml
- Ensure that the deployment for the "server" pod in helm/ can be configured with s3 configuration details
- Ensure that minio secrets can be specified in the hosted.values.yaml and be used via the deployment configuration
- Ensure that the hosted.values.yaml configuration has a configuration for s3
- Make any necessary updates to the storage abstraction that might be required to use s3 as a provider, if you find it to be deficient.
Coding standards
docs/AI_coding_standards.md