Promote InfraHouse repo/key convergence to global (production)#281
Merged
Conversation
Move profile::infrahouse_repo (+ converge-infrahouse-keyring.sh) into the global modules/profile that production uses (no env-local override), and wire the include into profile::base. Bundle the elastic::tls ca-certificates fix in the same change so production's elastic nodes never see the duplicate-declaration state that briefly hit sandbox (see #280). All four touched files are now byte-identical across global/development/sandbox, restoring the module-parity invariant from #276. Validated in development (jumphost + from-zero instance) and sandbox (elastic_master + jumphost, via SSM): catalog compiles, keyring == published bundle, source list byte-identical to cloud-init's seed, apt-get update clean. Note: the live release-noble bundle is still single-key; this class readies the fleet but the rotation only completes once the upstream new key is published into the bundle (before 2026-07-20). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
infrahouse8
approved these changes
Jul 4, 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
2 participants
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.
Phase 3 (final) of the keyring convergence plan: promote
profile::infrahouse_repointo the globalmodules/profilethat production uses.What
modules/profile/manifests/infrahouse_repo.pp+modules/profile/files/converge-infrahouse-keyring.sh(byte-identical to the validated dev/sandbox versions).include 'profile::infrahouse_repo'into globalprofile::base.package { 'ca-certificates' }from globalprofile::elastic::tls— bundled here so production's elastic nodes never hit the duplicate-declaration that briefly broke sandbox (Fix ca-certificates duplicate declaration on elastic nodes #280). Its file resources keeprequire => Package['ca-certificates'], now satisfied by base.All four touched files are byte-identical across global/development/sandbox, restoring the module-parity invariant from #276.
Why
cloud-init seeds the keyring + source list only at first boot, so long-lived instances never receive a rotated key. When the current noble signing key expires (2026-07-20),
apt-get updatewould fail fleet-wide withEXPKEYSIG. This class converges both artifacts every Puppet run.Validation carried in
ip-10-0-2-...): in-sync no-op, source byte-identical, keyring == bundle, rewrite path self-heals.elastic_masteri-0f554096e62f32ea0→puppet_exit=0+CONVERGED_OK;jumphosti-04c4cd399cd73d6a0→puppet_exit=0+CONVERGED_OK+ aptHit … noble InRelease.Rollout note
Fleet-wide production change. The live
release-noblebundle is still single-key — this readies the fleet, but the rotation only completes once the upstream new key is published into the bundle (the GATE), before 2026-07-20.🤖 Generated with Claude Code