opensafely-core / opensafely-core/backend-server
Capture outbound routing config in emis-access backend
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 5
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 2
Description
emis-access just manages users, no services.
However, it does need to ensure that its network routing is configured to use its assigned static IP for all outbound traffic.
This looks like adding the following to /etc/netplan/50-cloud-init.yaml config for eth0:
routes:
# as per https://docs.digitalocean.com/products/networking/reserved-ips/how-to/outbound-traffic/
- to: 0.0.0.0/0
via: 10.16.0.1
It may be that emis network access is changing, and we won't need this
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by checking whether emis network access still requires the outbound route, then locate how /etc/netplan/50-cloud-init.yaml is managed for eth0. Compare the configuration with the linked DigitalOcean guidance; done means the route is applied when still needed, or the issue is documented as unnecessary if networking has changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100