Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config_templates to services #18018

Open
StoffelCPR opened this issue Nov 15, 2024 · 0 comments
Open

Add config_templates to services #18018

StoffelCPR opened this issue Nov 15, 2024 · 0 comments
Labels
status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application

Comments

@StoffelCPR
Copy link

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

@StoffelCPR StoffelCPR added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

1 participant