Onboard arm64 build/enterprise roles (scaffolding; secrets empty)#44
Merged
Conversation
…lly empty) Extend the zero-touch vault path to the Apple Silicon build pools (M2), matching the M4 test family. Adds the four roles to the Secret Manager container list and the codified SCEP provisioner table: gecko_1_b_osx_arm64, gecko_3_b_osx_arm64, enterprise_1_b_osx_arm64, enterprise_3_b_osx_arm64 - terraform: 4 empty vault-<role> containers + per-secret broker IAM bindings (applied; 0 secret versions by design — values populated later, out of band). - bootstrap-step-ca.sh: 4 SCEP provisioners codified so a CA rebuild reproduces them. Deliberately NOT included (go-live steps, tracked separately): - Secret *values* (operator populates from 1P when ready). - Live `step ca provisioner add` for the four (operator runs the idempotent bootstrap-step-ca.sh, or adds them directly — causes a brief step-ca restart). - SimpleMDM "Dev - SCEP - <role>" profiles per device group. - L3 (gecko_3_b / enterprise_3_b) are release-trusted: per-role SCEP challenges recommended before their secrets are populated; and the Level-3 Chain-of-Trust signing key stays a manual, out-of-band step (NOT in the broker path) — see SECURITY.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Extends the zero-touch vault path to the Apple Silicon build pools (M2), matching the already-live M4 test family. Puts everything in place except the secret values (populated out-of-band later) and the SimpleMDM profiles.
Roles:
gecko_1_b_osx_arm64,gecko_3_b_osx_arm64,enterprise_1_b_osx_arm64,enterprise_3_b_osx_arm64.In this PR / already applied:
terraform/variables.tf— 4 roles added topuppet_roles→ 4 emptyvault-<role>Secret Manager containers + per-secret broker IAM bindings (applied via targetedterraform apply; verified 0 versions each).scripts/bootstrap-step-ca.sh— 4 SCEP provisioners codified (roles stamped into the SPIFFE template) so a CA rebuild reproduces them.Remaining go-live steps (not here, by design):
vault-<role>values from 1Password when ready.bootstrap-step-ca.sh, orstep ca provisioner add) — causes a brief step-ca restart, so operator-timed.Dev - SCEP - <role>profiles per device group.gecko_3_b/enterprise_3_b) are release-trusted: per-role SCEP challenges recommended before live secrets; the L3 Chain-of-Trust signing key remains a deliberate manual, out-of-band step (kept out of the broker path — seeSECURITY.md).🤖 Generated with Claude Code