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

Config context by tags #3664

Closed
itmicus opened this issue Nov 3, 2019 · 4 comments
Closed

Config context by tags #3664

itmicus opened this issue Nov 3, 2019 · 4 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@itmicus
Copy link

itmicus commented Nov 3, 2019

Environment

  • Python version: 3.7.3
  • NetBox version: 2.6.6

Proposed Functionality

Add to the config context assignment field with tags

Use Case

I use the tag "monitored_by_zabbix" for devices and VMs wich will be monitoring in our Zabbix system.
I want to create config contex with config for Zabbix for this devices/vms

Database Changes

Yes

External Dependencies

None

@kobayashi
Copy link
Contributor

Could you give us more detail of your usecase step-by-step?

@kobayashi kobayashi added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Nov 8, 2019
@wfrced
Copy link

wfrced commented Nov 15, 2019

I believe I have a somewhat similar usecase, so will chime in.
With these changes I'd be able to:

  1. Get a list of hosts using Netbox plugin for Ansible;
  2. Create Ansible groups using tag names and add my hosts to these groups;
  3. Add tag's Config Context to group variables;
  4. Create/Update hosts in Zabbix using Zabbix plugin for Ansible.

Basically, it would allow me to use tags as Ansible groups, and Config Contexts as group_vars.
Or I could simply store a more general Zabbix config for, say, a Tenant or a Site, and use tag's CC to store a boolean - whether to enable monitoring for this host.

@kobayashi kobayashi removed the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Nov 17, 2019
@stale
Copy link

stale bot commented Dec 6, 2019

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. Please see our contributing guide.

@stale stale bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Dec 6, 2019
@kobayashi kobayashi added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application and removed pending closure Requires immediate attention to avoid being closed for inactivity labels Dec 6, 2019
@kobayashi
Copy link
Contributor

I am taking this

@kobayashi kobayashi self-assigned this Dec 6, 2019
jeremystretch added a commit that referenced this issue Dec 11, 2019
@jeremystretch jeremystretch added this to the v2.7 milestone Dec 11, 2019
jeremystretch added a commit that referenced this issue Dec 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 10, 2020
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

4 participants