If I’m completely honest, after reading both your account and theirs, I don’t really understand why you’re this hung up about it.

It’s almost like you care more about credit than a port that actually works. I know you weren’t done/that it was a WIP, and they told you to wait, but at the end of the day it’s open software, and literally anyone could have beaten you to it.

I don’t think you’re wrong to feel that your efforts should have been represented more, but I honestly would have backed off like 10% through that conversation and just started working on something else. It’s not worth it man. I hope you can feel better about this whole situation soon.

The second option. With the first option you’ll end up in situations where you have spare compute/network resource that isn’t being utilised because all the remaining ones in the current batch of 100 are being handled by other threads / worker processes.

2 black bishops on black tiles

Not a DevOps eng so this might not be the most elegant answer but you could write an Ansible playbook to edit a hosts file on the target server and trigger that after deployment, within your CI/CD pipeline.

In an ideal situation, though, all your servers connect to a centralised DNS server (usually your gateway) where those domain names are managed.