chore: refresh Hero SSH known-hosts source - #67
Merged
Conversation
Contributor
OpenTofu TestOpenTofu test passed. View run output |
Contributor
OpenTofu PlanOpenTofu plan passed. View run outputOpenTofu will perform the following actions:
[REDACTED: potentially sensitive plan output]
[REDACTED: potentially sensitive plan output]
id = "hero-host-config:HERO_HOST_CONFIG_SSH_KNOWN_HOSTS"
~ plaintext_value = (sensitive value)
# (7 unchanged attributes hidden)
}
[REDACTED: potentially sensitive plan output]
[REDACTED: potentially sensitive plan output]
id = "tfroot-libvirt:SSH_KNOWN_HOSTS"
~ plaintext_value = (sensitive value)
# (8 unchanged attributes hidden)
}
Plan: 0 to add, 2 to change, 0 to destroy.
OpenTofu will perform the following actions:
[REDACTED: potentially sensitive plan output]
[REDACTED: potentially sensitive plan output]
id = "hero-host-config:HERO_HOST_CONFIG_SSH_KNOWN_HOSTS"
~ plaintext_value = (sensitive value)
# (7 unchanged attributes hidden)
}
[REDACTED: potentially sensitive plan output]
[REDACTED: potentially sensitive plan output]
id = "tfroot-libvirt:SSH_KNOWN_HOSTS"
~ plaintext_value = (sensitive value)
# (8 unchanged attributes hidden)
}
Plan: 0 to add, 2 to change, 0 to destroy. |
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.
Summary
Owner-authorized replacement of the canonical encrypted
ssh_known_hostssource after trusted out-of-band host-key verification. This branch changes onlysecrets/secrets.yaml; recipient mappings and workflow code are unchanged.Owner attestation: the intended operation is replacement of the canonical
ssh_known_hostsvalue while preserving SOPS recipient metadata. Commit metadata records three encrypted-file additions and three deletions. Ciphertext and plaintext were not retrieved, reviewed, or included here.Fixes # N/A
Type of change
Validation
opentofu / testandopentofu / plan; PR CI is the validation authority.Required plan review: confirm only the two existing Actions-secret instances are updated, with no recipient, repository-policy, provider, workflow, or other infrastructure drift. Do not include ciphertext, plaintext, credentials, private endpoints, raw logs, or sensitive plan output in review material.
After merge and the separately environment-gated
mainapply, dispatchhero-host-config's existing check-only workflow frommain. It must pass while retainingUserKnownHostsFileandStrictHostKeyChecking=yes; it is the functional gate before anytfroot-libvirtcleanup.Impact and rollout
Producer:
tfroot-githubremains the canonical encrypted source and Actions-secret distributor forssh_known_hosts.Consumers: the existing mapping updates both consumers atomically after the gated apply:
HERO_HOST_CONFIG_SSH_KNOWN_HOSTSinhero-host-configSSH_KNOWN_HOSTSintfroot-libvirtUnchanged: SOPS lookup/mapping code, recipients, provider pins, reusable workflow selection, Cloudflare configuration, SSH private-key sources, host configuration, GitOps desired state, and host mutation behavior.
Delivery stages: encrypted source authored and branch-published. PR test/plan are automatic and pending. Merge and
mainapply are separate confirmation gates. The WARP-routed, strict-SSH check-only workflow is a further manual confirmation-gated functional test. The deprecatedtfroot-libvirtcleanup remains separately reviewed and prohibited until that test passes.Rollback: before apply, close or revert this PR. After apply, restore a prior owner-validated encrypted source through a new PR and environment-gated apply; Actions secrets are not read back. Do not revert a compromised host key without an explicit owner security decision.
Safety and secrets
AI-assisted change: the owner authored and pushed the encrypted SOPS update. An OpenCode agent prepared this PR from non-secret metadata only; it did not retrieve, decrypt, print, or summarize encrypted secret content.