We can currently create jinja2 config_templates and add these to devices or virtual_machines.
To me personally it'd help my automation efforts somehwat if I could add these to services and maybe even service_templates
As example:
If I create a netbox service for a docker deployed netbox I could create the docker configuration as jinja2 template in netbox and then assign it to the service of the vm so ansible can pick it up and deploy netbox using docker and the information gathered from netbox ( not the best example but hey )
Use case
We could use the service feature more and extend the usability of that feature in ansible scripts.
NetBox version
v4.1.6
Feature type
Change to existing functionality
Triage priority
N/A
Proposed functionality
We can currently create jinja2 config_templates and add these to devices or virtual_machines.
To me personally it'd help my automation efforts somehwat if I could add these to services and maybe even service_templates
As example:
If I create a netbox service for a docker deployed netbox I could create the docker configuration as jinja2 template in netbox and then assign it to the service of the vm so ansible can pick it up and deploy netbox using docker and the information gathered from netbox ( not the best example but hey )
Use case
We could use the service feature more and extend the usability of that feature in ansible scripts.
It's mostly provisioning that benefits from this
Database changes
No response
External dependencies
No response