## Summary - Rename `date-modified` -> `modified` in all 80 docs and the `docs-check-frontmatter` task Quartz's `CreatedModifiedDate` plugin recognizes `modified`, `lastmod`, `updated`, and `last-modified` — but not `date-modified`. The wrong field name caused Quartz to ignore frontmatter dates entirely and fall through to filesystem timestamps (UTC inside Dagger), showing Feb 12 on pages built late on Feb 11 PST. ## Test plan - [x] `mise run docs-check-frontmatter` passes - [ ] Kick off docs release after merge — verify rendered dates match frontmatter values Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/158
1 KiB
1 KiB
| title | modified | tags | ||
|---|---|---|---|---|
| 1Password | 2026-02-10 |
|
1Password
Root credential store for all BlumeOps secrets, synced to Kubernetes via External Secrets Operator.
Architecture
1Password Cloud
|
v
1Password Connect (namespace: 1password)
|
v
External Secrets Operator (namespace: external-secrets)
|
v
Native Kubernetes Secrets
Vault
The blumeops vault contains all infrastructure credentials.
Kubernetes Integration
ClusterSecretStore: onepassword-blumeops
Services reference 1Password items via ExternalSecret manifests.
Disaster Recovery Backup
The mise run op-backup task encrypts a .1pux vault export and transfers it to indri for inclusion in borgmatic backups. See restore-1password-backup for the full recovery procedure.
Related
- argocd - Uses secrets for git access
- postgresql - Database credentials
- restore-1password-backup - Recovery from backup
- borgmatic - Backup system