Allow for configurable repo for archive downloads #357
Conversation
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
|
Amplify deployment status
|
Before #307, external contributors to the docs could preview their contributions on AWS Amplify using `gravitational/teleport` forks by entering their fork URL into the `.gitmodules` configuration. There is no such possibility for the current site, since the `download-content-archive.sh` script hard-codes the GitHub repository from which it downloads archives. This change adds an optional `repo_path` field to each version metadata object in `config.json`. External contributors can specify a repository path such as "myfork/teleport" for a version, and the `download-content-archive.sh` script fetches a tarball from the fork for that version's content directory.
c0486dd to
8490185
Compare
8490185 to
6fd06df
Compare
taraspos
approved these changes
Sep 16, 2025
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.
Before #307, external contributors to the docs could preview their contributions on AWS Amplify using
gravitational/teleportforks by entering their fork URL into the.gitmodulesconfiguration. There is no such possibility for the current site, since thedownload-content-archive.shscript hard-codes the GitHub repository from which it downloads archives.This change adds an optional
repo_pathfield to each version metadata object inconfig.json. External contributors can specify a repository path such as "myfork/teleport" for a version, and thedownload-content-archive.shscript fetches a tarball from the fork for that version's content directory.