feat(mirrors,get) monitor http to https enforced redirection and use the same pattern for get and mirrors #88
Conversation
Signed-off-by: Damien Duportal <[email protected]>
…the same pattern for get and mirrors Signed-off-by: Damien Duportal <[email protected]>
Signed-off-by: Damien Duportal <[email protected]>
| resource "datadog_synthetics_test" "mirrors_jenkinsci_org" { | ||
| type = "api" | ||
| request_definition { | ||
| method = "GET" | ||
| url = "https://mirrors.jenkins-ci.org" | ||
| url = "https://mirrors.jenkins-ci.org/debian/jenkins_2.251_all.deb?mirrorlist" |
There was a problem hiding this comment.
Will this version have to be updated in the future?
There was a problem hiding this comment.
nope: a given version must always be available through the mirrors.
The idea is to monitor the whole service (e.g. "does it work as expected?") and not only the HTTP answer. By providing a full URL to an existing file, with the query string parameter mirrorlist, then we expect the HTTP/200 page.
Since mirrorbits does not have the file itself (it is expected to answer an HTTP/3XX redirect to a mirror), an HTTP/200 only means that we have the full-featured service.
=> this was the behavior of the monitor on get.jenkins.io, so this change is to make it coherent (as the 3 domains get.jenkins.io, mirrors.jenkins.io and mirrors.jenkins-ci.org are pointing towards the same service)
Why this change? #85 (comment)
The goal is to monitor the enforced HTTP to HTTPS redirection introduced by the actions in jenkins-infra/helpdesk#2888 (consildating the DNS mirrors.jenkins* to the kubernetes-hosted mirrorbits service, same as get.jenkins.io).