"CBN" revalidation on the firewall holes for the release team.
Open
@ryanaslett is already working on this.
Since Sep 1, 2026.
build-agenda
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
As mentioned in slack we should go through the firewall rules on the staging server and remove some of the old "holes" that we have in there. Since we log them all in the configuration files against the user that requested them this should be fairly easy.
(I use the term CBN in the title as "Continued Business Need" which is what needs to be checked)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.