ca02340a4c
Replace the confused Profile abstraction with a dedicated Secret resource
following Kubernetes conventions. Servers now have env entries with inline
values or secretRef references. Env vars are resolved and passed to
containers at startup (fixes existing gap).
- Add Secret CRUD (model, repo, service, routes, CLI commands)
- Server env: {name, value} or {name, valueFrom: {secretRef: {name, key}}}
- Add env-resolver utility shared by instance startup and config generation
- Remove all profile-related code (models, services, routes, CLI, tests)
- Update backup/restore for secrets instead of profiles
- describe secret masks values by default, --show-values to reveal
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
7 lines
433 B
TypeScript
7 lines
433 B
TypeScript
export { BackupService } from './backup-service.js';
|
|
export type { BackupBundle, BackupServer, BackupSecret, BackupProject, BackupOptions } from './backup-service.js';
|
|
export { RestoreService } from './restore-service.js';
|
|
export type { RestoreOptions, RestoreResult, ConflictStrategy } from './restore-service.js';
|
|
export { encrypt, decrypt, isSensitiveKey } from './crypto.js';
|
|
export type { EncryptedPayload } from './crypto.js';
|