🛠️ Fix: Azure status badge creation #10
Merged
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.
What's this PR do?
Fixes Azure env vars that are intended to create a status badge indicating whether a spider successfully ran or failed during the cron workflow.
Why are we doing this?
This env var misconfiguration issue was causing the status badge to not be created when a spider successfully runs or fails in prod. It has been observed in a number of city-scraper repos.
Steps to manually test
Are there any smells or added technical debt to note?
n/a