Add config_templates to services #10479

Closed
opened 2025-12-29 21:32:01 +01:00 by adam · 4 comments
Owner

Originally created by @StoffelCPR on GitHub (Nov 15, 2024).

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

Originally created by @StoffelCPR on GitHub (Nov 15, 2024). ### 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_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:32:01 +01:00
adam closed this issue 2025-12-29 21:32:01 +01:00
Author
Owner

@StoffelCPR commented on GitHub (Dec 4, 2024):

Same goes for config_contexts. I can assign them to tags but don't get them in the ansible inventory. It'd be nice to assign these to services as well.

@StoffelCPR commented on GitHub (Dec 4, 2024): Same goes for config_contexts. I can assign them to tags but don't get them in the ansible inventory. It'd be nice to assign these to services as well.
Author
Owner

@jeremystretch commented on GitHub (Feb 6, 2025):

We could use the service feature more and extend the usability of that feature in ansible scripts.

The service model in NetBox is intended merely to represent layer 7 services (e.g. HTTPS, SSH, etc.) available on a node. It sounds like maybe you're using it for something more than that. Could you elaborate on your use case?

@jeremystretch commented on GitHub (Feb 6, 2025): > We could use the service feature more and extend the usability of that feature in ansible scripts. The service model in NetBox is intended merely to represent layer 7 services (e.g. HTTPS, SSH, etc.) available on a node. It sounds like maybe you're using it for something more than that. Could you elaborate on your use case?
Author
Owner

@github-actions[bot] commented on GitHub (Feb 14, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Feb 14, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 21, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Feb 21, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10479