Config context schemas
One of the differences between Nautobot’s data model and a traditional Infrastructure as Code (IaC) model defined in structured data, such as YAML or JSON, is that the models are stored in databases, and thus naturally enforce a schema. This ensures things such as “If a device is added, it must have a Location” or “If the config context is active, it must be a Boolean value.”
However, config contexts act more like IaC, in that anyone can technically type in any value they want. So, instead of typing in “true” for active, you can type in “sure” or type in an IP address of “300.1.1.1” as one of your NTP servers. This is problematic because any programmatic access likely expects a valid Boolean and a valid IP, respectively.
Fortunately, a spec exists called json-schemas (https://json-schema.org/) that allows you to describe your data model and enforce that the data defined adheres...
