@@ -16,6 +16,7 @@ at [https://netboxlabs.com/blog/introducing-diode-streamlining-data-ingestion-in
1616| :--------------:| :--------------:|
1717| >= 3.7.2 | 0.1.0 |
1818| >= 4.1.0 | 0.4.0 |
19+ | >= 4.2.3 | 1.0.0 |
1920
2021## Installation
2122
@@ -46,32 +47,18 @@ Also in your `configuration.py` file, in order to customise the plugin settings,
4647``` python
4748PLUGINS_CONFIG = {
4849 " netbox_diode_plugin" : {
49- # Auto-provision users for Diode plugin
50- " auto_provision_users" : False ,
51-
5250 # Diode gRPC target for communication with Diode server
5351 " diode_target_override" : " grpc://localhost:8080/diode" ,
5452
55- # User allowed for Diode to NetBox communication
56- " diode_to_netbox_username" : " diode-to-netbox" ,
57-
58- # User allowed for NetBox to Diode communication
59- " netbox_to_diode_username" : " netbox-to-diode" ,
60-
61- # User allowed for data ingestion
62- " diode_username" : " diode-ingestion" ,
53+ # Username associated with changes applied via plugin
54+ " diode_username" : " diode" ,
6355 },
6456}
6557```
6658
6759Note: Once you customise usernames with PLUGINS_CONFIG during first installation, you should not change or remove them
6860later on. Doing so will cause the plugin to stop working properly.
6961
70- ` auto_provision_users ` is a boolean flag (default: ` False ` ) that determines whether the plugin should automatically
71- create the users during
72- migration. If set to ` False ` , you will need to provision Diode users with their API keys manually via the plugin's setup
73- page in the NetBox UI.
74-
7562Restart NetBox services to load the plugin:
7663
7764```
@@ -89,28 +76,6 @@ cd /opt/netbox
8976source venv/bin/activate
9077```
9178
92- Three API keys will be needed (these are random 40 character long alphanumeric strings). They can be generated and set
93- to the appropriate environment variables with the following commands:
94-
95- ``` shell
96- # API key for the Diode service to interact with NetBox
97- export DIODE_TO_NETBOX_API_KEY=$( head -c20 < /dev/urandom| xxd -p) ; env | grep DIODE_TO_NETBOX_API_KEY
98- # API key for the NetBox service to interact with Diode
99- export NETBOX_TO_DIODE_API_KEY=$( head -c20 < /dev/urandom| xxd -p) ; env | grep NETBOX_TO_DIODE_API_KEY
100- # API key for Diode SDKs to ingest data into Diode
101- export DIODE_API_KEY=$( head -c20 < /dev/urandom| xxd -p) ; env | grep DIODE_API_KEY
102- ```
103-
104- ** Note:** store these API key strings in a safe place as they will be needed later to configure the Diode server.
105-
106- If you don't set these environment variables, the plugin will generate random API keys for you either during the
107- migration process (with ` auto_provision_users ` set to ` True ` ) or when you manually create the users in the plugin's
108- setup page in the NetBox UI.
109-
110- It's important to note that environment variables with API keys should be populated in the Diode server's
111- environment variables (see [ docs] ( https://github.com/netboxlabs/diode/tree/develop/diode-server#running-the-diode-server ) )
112- as well to ensure proper communication between the Diode SDK, Diode server and the NetBox plugin.
113-
11479Run migrations to create all necessary resources:
11580
11681``` shell
0 commit comments