feat(managed-secrets): add centrally managed secrets with GITOPS_ prefix pushed to multiple targets
Introduce managed secrets owned by GitOps that can be defined once and
pushed to any combination of projects/groups across connections. Values
are stored in OS keychain, secrets appear on targets as GITOPS_{key}.
This commit is contained in:
10
changelog.md
10
changelog.md
@@ -1,5 +1,15 @@
|
||||
# Changelog
|
||||
|
||||
## 2026-02-28 - 2.10.0 - feat(managed-secrets)
|
||||
add centrally managed secrets with GITOPS_ prefix pushed to multiple targets
|
||||
|
||||
- Add IManagedSecret, IManagedSecretTarget, IManagedSecretStored interfaces and TypedRequest contracts for CRUD + push operations
|
||||
- Add ManagedSecretsManager with keychain-backed storage, upsert push logic, target diff on update, and best-effort delete
|
||||
- Add ManagedSecretsHandler with 7 endpoints wired into OpsServer with auth guards and action logging
|
||||
- Add frontend state part, 6 appstate actions, and Managed Secrets view with table, target picker, and push/edit/delete modals
|
||||
- Add Managed Secrets tab to dashboard after Secrets
|
||||
- Extend action log types with 'managed-secret' entity and 'push' action
|
||||
|
||||
## 2026-02-28 - 2.9.0 - feat(sync)
|
||||
remove target avatar when source has none to keep avatars fully in sync
|
||||
|
||||
|
||||
Reference in New Issue
Block a user