Purge the private docs Fastly service for private repositories#137
Merged
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
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.
Makes hexdocs cache purging repository-aware. Private repositories' docs are now edge-cached by the new
docs-privateFastly compute service, so publish/delete of private docs must purge that service (:fastly_hexdocs_private) rather than the public one. The public hexpm path is unchanged.purge/2selects:fastly_hexdocs_privatefor non-hexpm repositories viapublic?/1purge_hexdocs_cache/4is generalized from hardcoded"hexpm"to any repositoryHEXDOCS_FASTLY_HEXDOCS_PRIVATE(the prod docs-private service id) is wired into runtime config; the Fastly adapter resolves it genericallyDeploy ordering: the prod deployment config map must already provide
HEXDOCS_FASTLY_HEXDOCS_PRIVATE(fail-fast on boot) — set via the hexpm-ops docs-private service.