Add management command to delete redirects to torchbox.com on staging

[helenb]

Description of Changes Made

On staging we have a bunch of redirects which all point to a torchbox.com url. This is as a result of importing the production data. It's potentially very confusing, as people might not notice the redirect - and in a worst case scenario they might accidentally edit a live page with a test thinking they are on staging. This PR adds a management command that allows you to delete all redirects pointing to a http://torchbox.com url. At the moment it excludes any media.torchbox.com redirects.

How to Test

Try running the script in your local build. Note that as a precaution it can't be run in production.

Screenshots

Expand to see more

MR Checklist

• Add a description of your pull request and instructions for the reviewer to verify your work.
• If your pull request is for a specific ticket, link to it in the description.
• Stay on point and keep it small so the merge request can be easily reviewed.
• Tests and linting passes.

Unit tests

• Added
• Not required

Documentation

• Updated build docs
• Updated editor guidelines (See https://intranet.torchbox.com/torchbox-com-project-docs for the private link, for Torchbox employees only)
• Updated field spec (See https://intranet.torchbox.com/torchbox-com-project-docs for the private link, for Torchbox employees only)
• Not required

Browser testing

• I have tested in the following browsers and environments (edit the list as required)
  • Latest version of Chrome on mac
  • Latest version of Firefox on mac
  • Latest version of Safari on mac
  • Safari on last two versions of iOS
  • Chrome on last two versions of Android
• Not required

Data protection

• Not relevant
• This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Light and dark mode

• I have tested the changes in both light and dark mode
• The change is not relevant to dark and light mode

Accessibility

• Automated WCAG 2.1 tests pass
• HTML validation passes
• Manual WCAG 2.1 tests completed
• I have tested in a screen reader
• I have tested in high-contrast mode
• Any animations removed for prefers-reduced-motion
• Not required

Sustainability

• Images are optimised and lazy-loading used where appropriate
• SVGs have been optimised
• Performance and transfer of data considered
• If JavaScript is needed alternatives have been considered
• Not required

Pattern library

• The pattern library component for this template displays correctly, and does not break parent templates
• The styleguide is updated if relevant
• [x} Changes are not relevant the pattern library

[zerolab]

q: would it not make more sense to replace with the staging domain?
Also, what are the safeguards against running this in prod? e.g. it may be more fitting as a birdbath extension

[helenb]

q: would it not make more sense to replace with the staging domain?

We could do - but to be honest there are hundreds of old redirects and I think it just makes more sense to not have them on staging - e.g. there are ones created as shortlinks for webinars.

q: Also, what are the safeguards against running this in prod? e.g. it may be more fitting as a birdbath extension

It checks the sentry env with if sentry_env == "production": - I hadn't thought of making it part of birdbath. If I get a sec I will try doing that instead. It might be good though to be able to run this on staging sooner rather than later as there is a danger of people accidentally landing on production and making test changes when they think they are on staging.

[zerolab]

It might be good though to be able to run this on staging sooner rather than later as there is a danger of people accidentally landing on production and making test changes when they think they are on staging.

perphas best done via the CLI as a one-off?