docs(baton): show how to mount GitHub App private key in Kubernetes - #465
Merged
Conversation
Both the GitHub and GitHub Enterprise Cloud self-hosted setup guides referenced BATON_APP_PRIVATEKEY_PATH without showing how the key file actually gets onto the container filesystem. Add a Secret + volume mount example, consistent with the pattern already used in successfactors-scim.mdx. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Collaborator
Author
|
@ennyjfrick if you approve these changes, we'll also need to update the upstream docs in the baton-github and baton-github-enterprise-cloud connector repos so they stay in sync. |
Collaborator
Author
|
Follow-up done: opened upstream ports of this fix —
(Note: the enterprise-cloud connector repo is actually named |
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
BATON_APP_PRIVATEKEY_PATHbut never show how to get the private key file onto the connector container's filesystem at that path.volumeMounts/volumesexample in the Deployment manifest, mirroring the existing pattern insuccessfactors-scim.mdxand the Kubernetes secret-volume guide.Test plan