Content management considerations and Git
The first thing that we must consider when creating code files is how to keep them in a location where they can be retrieved and used by us and others. Ideally, this location would be the only central place where the file is kept but also have backup copies available if needed. After the initial release of the code, we might add features and fix bugs in the future, so we would like a way to track these changes and keep the latest ones available for download. If the new changes do not work, we would like ways to roll back the changes and reflect the differences in the history of the file. This would give us a good idea of the evolution of the code files.
The second question is about the collaborative process between our team members. If we work with other network engineers, we will most likely need to work collectively on the files. These can be Python scripts, Ansible Playbooks, Jinja2 templates, INI-style configuration files, and many...
