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

ability to add custom links to config templates #14366

Closed
rrizun opened this issue Nov 28, 2023 · 2 comments · Fixed by #15411
Closed

ability to add custom links to config templates #14366

rrizun opened this issue Nov 28, 2023 · 2 comments · Fixed by #15411
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@rrizun
Copy link

rrizun commented Nov 28, 2023

NetBox version

v3.6.5

Feature type

Data model extension

Proposed functionality

ability to add custom links to config templates .. the custom link 'content-types' selection ( here: https://demo.netbox.dev/extras/custom-links/add/ ) has many netbox object types .. but config-templates is currently not one of them

implementation-wise I think this means adding CustomLinksMixin to ConfigTemplate model amongst other things?

so, proposed functionality here would mean to add "Extras > Config Template" to the custom-link content-types drop down selection

Use case

my use case is I would like to add a custom link to a config template so that I can render the template using 'general purpose use' https://docs.netbox.dev/en/stable/features/configuration-rendering/ .. in my use case I use templates in situations other than per-device situations .. being able to add a custom-link will let me point to my custom script do perform custom rendering of the config template

Database changes

No response

External dependencies

No response

@rrizun rrizun added the type: feature Introduction of new functionality to the application label Nov 28, 2023
@jeremystretch
Copy link
Member

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch jeremystretch added status: revisions needed This issue requires additional information to be actionable and removed status: revisions needed This issue requires additional information to be actionable labels Nov 28, 2023
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Feb 28, 2024
@jeremystretch jeremystretch self-assigned this Mar 12, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed pending closure Requires immediate attention to avoid being closed for inactivity labels Mar 12, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants