DNS as code and continuous deployment with OctoDNS

# Old process
1 - Technician receives a ticket
2 - Technician uses some custom script to deploy the changes to the main provider
3 - Technician resolves the ticket
----------------------------------------
# New process
1 - Technician receives a ticket
2 - Technician apply the changes in the OctoDNS configuration and commit his changes in git with the ticket ID in the commit message and pushes the changes to the central git repository
4 - Bamboo verify the config is valid and deploys it to all providers
5 - Bamboo notify the entire team about the recent changes
6 - Technician resolves the ticket
OctoDNS configuration is easy to understand

--

--

DevOps @ MindGeek Canada

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store