Repository navigation
chore(secrets): trinity's ntfy and Homepage keys, encrypted (#136, #137) - #717
Merged
Merged
Conversation
The eight keys the two services' compose guards require, as added on
trinity with `make secrets-edit STACK=sensitive`: NTFY_ALERTMANAGER_TOKEN,
NTFY_ALERTMANAGER_PASSWORD_HASH, NTFY_PHONE_PASSWORD_HASH,
NTFY_TOPIC_{ALERTS,URGENT,SECURITY}, HOMEPAGE_IMMICH_API_KEY and
HOMEPAGE_PAPERLESS_TOKEN. Every value is ENC[AES256_GCM,...] to the
`sensitive` rule's recipients, and check-sops-encrypted.sh passes.
Committed so the deployment checkout on trinity is clean again. It is
byte-identical to the file there.
Refs #136
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
secrets/sensitive.sops.yamlgains the eight keys the ntfy (#136) and Homepage (#137) compose guards require:NTFY_*keysHOMEPAGE_IMMICH_API_KEYHOMEPAGE_PAPERLESS_TOKENThey were added on trinity with
make secrets-edit STACK=sensitiveduring the cutover. This commits them in encrypted form.Why
The tracked secrets file on trinity's deployment checkout was modified and uncommitted. Committing it clears that, and the repository matches what trinity runs.
Blast radius
None at runtime. The file is byte-identical to the one trinity already renders from, so no service changes.
After merge, trinity's checkout needs
git checkout -- secrets/sensitive.sops.yaml && git pull --ff-only, because a pull won't overwrite a modified file even when the incoming content is identical.No change to network segmentation or firewall rules
No new port published to a VLAN that could not already reach the service
No credential added outside
secrets/*.sops.yaml: every value isENC[AES256_GCM,…]Verification
Encrypted:
check-sops-encrypted.shpasses (4 SOPS files, all encrypted), and all 15 keys' values areENC[AES256_GCM,…].Right recipients:
check_sops_rules.pypasses, so the file matches thesensitiverule.Identical:
cmpagainst trinity's working copy found no difference.make validatechecks run (secrets section)Deployed: this is the file trinity already runs from
Docs: n/a
Refs #136
🤖 Generated with Claude Code