From 92e9a1149c32ca78a0982d911046a083bea5e6e6 Mon Sep 17 00:00:00 2001 From: Twan Kamans Date: Fri, 16 Jul 2021 20:02:08 +0200 Subject: [PATCH] Updated README with Proxy details and -p flag --- README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ccb5890..e69f114 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ Optional: | -t | tenant | Add the tenant name to the hostgroup format (Tenant/Site/Manufacturer/Role) | | -s | secret | Use Netbox secrets if present on device for SNMP parameters | -v | verbose | Log with debugging on. | - +| -p | proxy-power | Force a full proxy sync. USE WITH CAUTION, see "Set proxy within Netbox" for more information | #### Logging Logs are generated under sync.log, use -v for debugging. @@ -56,6 +56,17 @@ And this field for the Zabbix template * Default: null * Object: dcim > device_type +#### Set proxy within Netbox +You can set the proxy for a device using the 'proxy' key in config context. +```json +{ + "zabbix": { + "proxy": "yourawesomeproxy.local" + } +} +``` +Because of the posible amount of destruction when setting up Netbox but forgetting the proxy command, the sync works a bit different. By default everything is synced except in a situation where the Zabbix host has a proxy configured but nothing is configured in Netbox. To force deletion and a full sync, use the -p flag. + #### Set interface parameters within Netbox When adding a new device, you can set the interface type with custom context. Due to Zabbix limitations of changing interface type with a linked template, changing the interface type from within Netbox is not supported and the script will generate an error.