Repository navigation
fix: the rollout report's health check names itself, so Cloudflare does not refuse it - #51
Merged
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.
graphite-reportchecks each project's host after a rollout. It sent Python's defaultPython-urllibuser agent, which Cloudflare refuses with 403. So the hub recordedhealthStatus: 403for its own deploy, although the site answers/with 200.The check now sends
User-Agent: project-graphite-deploy-report, the same kind of named agent the uptime check uses.Checked from outside against
https://project-graphite.com/:Python-urllib/3.12gets 403,project-graphite-deploy-reportgets 200. The script still parses.After merge, copy the script to the VPS again;
host/files travel only throughbootstrap.sh:sudo curl -fsSL -o /srv/graphite/bin/graphite-report https://raw.githubusercontent.com/project-graphite/platform/main/host/graphite-report sudo chmod 755 /srv/graphite/bin/graphite-report && sudo chown deploy:deploy /srv/graphite/bin/graphite-reportProjects behind Cloudflare Access, such as the console, still report 403, which is Access answering, as expected.