Repository navigation
docs(full-platform): record the github app authentication setup - #46
Merged
Merged
Conversation
Juanmadiaz45
changed the title
Juanmadiaz45
force-pushed
the
docs/github-app-authentication
branch
from
September 14, 2026 17:20
4c1abd0 to
d5c3a39
Compare
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 changes
Adds
full-platform/github-app-authentication.md, documenting the two org-owned GitHub Apps backing.github'srelease.yml/promote.ymlreusable workflows: exact permissions, single-vs-selected repository installation scope, the selected-repository organization secret names each caller wires, mode-0600 private-key upload/cleanup discipline, a zero-downtime rotation procedure, and the fail-closed authority checks already enforced in code (tuple validation, Cosign verification, no-self-approval).Why
Spec 009 T103 requires this setup to be reviewed and recorded, not left implicit in workflow YAML. The two Apps are already created and connected (organization-owned, already functional in
.github'srelease.yml/promote.yml); this PR is the missing documentation artifact, derived directly from what those two workflow files actually do.Tasks
bootstrap-sonarqube.shhelper and its tests are delivered in amicroservice-app-gitopsPR)How it is verified
.github/.github/workflows/release.ymlandpromote.ymlsource (App-id/key secret names,repositories:scoping, tuple validation, Cosign verification) and against.github/tests/workflows/reusable-workflow-contract.bats's assertions (SHA-pinnedcreate-github-app-token, no static AWS credentials).Risk and rollback
None: documentation only, no workflow or code change. Rollback is
git revertthis commit.What this PR does not do
Does not create, reconfigure, or rotate either GitHub App (both already exist and are functional); does not change
release.yml/promote.yml; does not touch the SonarQube bootstrap tooling (separate PR inmicroservice-app-gitops).