This repository has been archived by the owner. It is now read-only.
Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign up[dev.icinga.com #4390] show custom variables in extended info, allow to exclude name/value containing defined config options #1303
Labels
Milestone
Comments
This comment has been minimized.
This comment has been minimized.
Updated by mfriedrich on 2013-07-06 14:09:57 +00:00
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Updated by mfriedrich on 2013-09-11 22:42:59 +00:00 looks nice :) |
This comment has been minimized.
This comment has been minimized.
Updated by ricardo on 2013-09-12 18:10:54 +00:00
|
This comment has been minimized.
This comment has been minimized.
Updated by mfriedrich on 2014-12-08 09:15:29 +00:00
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue has been migrated from Redmine: https://dev.icinga.com/issues/4390
Created by mfriedrich on 2013-07-06 13:51:11 +00:00
Assignee: ricardo
Status: Resolved (closed on 2013-09-12 18:10:54 +00:00)
Target Version: 1.10
Last Update: 2014-12-08 09:15:29 +00:00 (in Redmine)
Having Icinga2 Compat on my plate, I wanted to test the "custom dictionary to customvar name/value" functionality with objects.cache until I realized that the Classic UI does not support custom variables at all.
It's not quite true, as the hosts and services have already read all custom variables into memory, so accessing them is quite easy. The actual hard part is - well known from Icinga Web - that you must exclude sensitive information like passwords, snmp communities etc.
For that reason, cgi.cfg should include 2 new options
basically the exclude works like the database 'LIKE pattern' in order to filter everything just by the pattern, and not the exact match. If you pass '*' all names/values will be filtered (makes sense in some installations).
the parser should be as modular as the parsing for authorization information already is (hooray for Ricardo's macro magic).
location on the screen - either somewhere on the state information, or a seperated table next to the enable/disable options. will only be shown if there are actually custom vars set for this host/service.
Attachments
Changesets
2013-07-06 14:02:04 +00:00 by (unknown) 02ac61c
2013-09-11 20:14:18 +00:00 by ricardo 6866528
2013-09-21 16:07:36 +00:00 by ricardo a8c110b
2013-09-21 16:49:48 +00:00 by ricardo c0694a6
2013-09-21 18:34:14 +00:00 by ricardo 7a4ad61
2013-09-21 18:37:31 +00:00 by ricardo aa77900