This PR removes the slo, ci_url and uptime_url keys from the service.yml file. We are rolling out this change across Shopify for all services.
Why?
slo: SLOs are no longer required to be defined in service.yml file, instead, they should be created in Observe. It is highly recommended to define an availability SLO for your service.
ci_url: there's no need to override the CI pipeline url, the statistical CI information can be found in the CI Metrics tab in Services DB.
uptime_url: overriding uptime monitor url in service.yml is no longer supported, please go to Services DB page to define or link any uptime monitor.
Please checkout the document to find more information about the supported service properties.
Where can I get help?
The service.yml changes in this pull request were generated programmatically, so it may have accidentally deleted comments or aliases.
Feel free to touch up the pull request to match whatever style you'd like before merging. If you have any questions, please reach out to #help-eng-infrastructure on Slack.
Please review, fix any issues, and merge this PR.
This PR removes the
slo,ci_urlanduptime_urlkeys from theservice.ymlfile. We are rolling out this change across Shopify for all services.Why?
slo: SLOs are no longer required to be defined inservice.ymlfile, instead, they should be created in Observe. It is highly recommended to define an availability SLO for your service.ci_url: there's no need to override the CI pipeline url, the statistical CI information can be found in theCI Metricstab in Services DB.uptime_url: overriding uptime monitor url inservice.ymlis no longer supported, please go to Services DB page to define or link any uptime monitor.Please checkout the document to find more information about the supported service properties.
Where can I get help?
The
service.ymlchanges in this pull request were generated programmatically, so it may have accidentally deleted comments or aliases. Feel free to touch up the pull request to match whatever style you'd like before merging. If you have any questions, please reach out to #help-eng-infrastructure on Slack.