Managing data with config contexts and using Git
It may be evident by now, but let’s look at common scenarios where you would choose to use config contexts with Nautobot and Git:
- Adding a network change locally, for example, adding a new BGP peer in the right config context YAML file:
- Consider creating a JSON Schema definition to ensure the data adheres to your standard data model
- You should follow good Git practices as well, for example, create a new branch that holds the new changes
- Opening a pull request to the repo.
- Allowing your team to review, comment on, and then finally merge your pull request.
- Syncing a Nautobot Git repo (on a schedule, in the UI, or using the API, and possibly even from a webhook upon merge).
- Executing automation such as an Ansible playbook that’ll then use the updated data, such as adding a new BGP peer.
For more use cases, please do not forget to consider how to add a specific feature, remove a feature, or simply...
