Skip to content

Conversation

devin-ai-integration[bot]
Copy link
Contributor

Add self-hosted Patcher binaries documentation (DEV-1044)

Summary

This PR adds comprehensive documentation at docs/2.0/docs/patcher/installation/self-hosted.md explaining how to use Patcher with self-hosted binaries for enterprise customers with network restrictions or security policies requiring internal hosting of dependencies.

The documentation covers a two-step process: using repo-copier to copy Patcher/Terrapatch binaries to internal repositories, then configuring the GitHub Action with new parameters from the feat-custom-org branch (scm_type, scm_base_url, scm_org, patcher_git_repo, terrapatch_git_repo, terrapatch_scm_org).

Includes practical YAML examples for GitHub Enterprise, GitLab, troubleshooting guidance, and explains why Artifactory is not currently supported.

Review & Testing Checklist for Human

  • Verify self-hosted parameters match actual implementation - The documented parameters (scm_type, scm_base_url, etc.) were sourced from the feat-custom-org branch and need validation against the final implementation
  • Test YAML examples are syntactically valid - The GitHub Action YAML examples should be copy-pasteable and work without syntax errors
  • Check internal documentation links work - Verify links to /2.0/docs/library/guides/self-hosting, /2.0/docs/patcher/guides/troubleshooting and other internal docs resolve correctly
  • Validate repo-copier usage examples - Confirm the repo-copier command examples match current tool syntax and best practices

Test Plan Recommendation

  1. Create a test workflow using one of the provided YAML examples
  2. Verify the parameter table matches the actual action.yml inputs in the feat-custom-org branch
  3. Click through all internal documentation links to ensure they resolve
  4. Review repo-copier examples against the actual tool documentation

Notes

- Create comprehensive guide for using Patcher with self-hosted binaries
- Document new parameters from feat-custom-org branch for custom SCM providers
- Include GitHub Enterprise and GitLab configuration examples
- Reference repo-copier usage and existing Library documentation
- Add troubleshooting section and Artifactory limitations
- Addresses DEV-1044 requirements for enterprise customers with network restrictions

Co-Authored-By: Josh Padnick <[email protected]>
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link
Contributor

coderabbitai bot commented Aug 29, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

vercel bot commented Aug 29, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Aug 29, 2025 9:48pm

- Remove reference to non-existent troubleshooting guide
- Replace with general reference to Patcher documentation
- Resolves validate_build and Vercel deployment CI failures

Co-Authored-By: Josh Padnick <[email protected]>
- Use second person throughout following Boise State writing guidelines
- Reorganize to present two main self-hosting options clearly
- Remove GitLab examples, replace with support email instruction
- Remove repo-copier code examples and version management section
- Update section headers (New self-hosted parameters → GitHub Actions parameters)
- Move Artifactory limitations to bottom of document
- Improve overall document flow and user-focused language

Co-Authored-By: Josh Padnick <[email protected]>
- Add back repo-copier code examples showing how to copy patcher-cli and terrapatch-cli
- Clarify that Patcher scans code/updates files, Terrapatch does transformations
- Explain that all Patcher customers have access to github.com/gruntwork-io/patcher-cli
- Update GitLab section to reflect that support is new, direct to support email
- Emphasize that only binaries need self-hosting, not the service itself
- Change 'Example configuration' to 'Example configurations' for consistency

Co-Authored-By: Josh Padnick <[email protected]>
@josh-padnick
Copy link
Contributor

Closing in favor of #2722.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant