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

Allow Custom Links to be enabled/disabled #8296

Closed
rodvand opened this issue Jan 9, 2022 · 1 comment
Closed

Allow Custom Links to be enabled/disabled #8296

rodvand opened this issue Jan 9, 2022 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@rodvand
Copy link
Contributor

rodvand commented Jan 9, 2022

NetBox version

v3.1.5

Feature type

Data model extension

Proposed functionality

Add the option to disable a custom link.

Use case

When utilising various plugins in NetBox we sometimes use URLs to access the plugin data. Plugins aren't always updated to support the latest and greatest NetBox version straight away so we disable the plugin for upgrades (we must be on the latest NetBox, of course!). To avoid user confusion I remove the custom links referencing the plugin. And when the plugin author updates the plugin I add the custom link back to NetBox. Having an enabled toggle on the custom link would save me some work.

Database changes

Have to add a field to the CustomLink model. Something like this I suspect:

enabled = models.BooleanField(
        default=True
    )

External dependencies

No response

@rodvand rodvand added the type: feature Introduction of new functionality to the application label Jan 9, 2022
@jeremystretch
Copy link
Member

Probably something we should have implemented originally, the same way we allow enabling and disabling webhooks. I'm going to tag this for v3.2 as it's very easy to implement (but will effect an API change).

@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Jan 10, 2022
@jeremystretch jeremystretch added this to the v3.2 milestone Jan 10, 2022
@jeremystretch jeremystretch self-assigned this Jan 10, 2022
This was referenced Apr 5, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 11, 2022
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

No branches or pull requests

2 participants