-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Can't add multiple proxmox clusters to proxbox PLUGINS_CONFIG block. Issue with dict vs list #150
Comments
I pushed a commit that seems to solve this issue. Unfortunately I also pushed another commit that contains a password + token fallback workaround (a little quality of life improvement). I can revert my branch back to its "fix-only" state if such PR is unacceptable (given that two commits are being merged). |
I have got the same issue
After removing the lists from inside the proxmox dictionary I've run into another error
Will wait to see what is done here before opening a separate issue for my second error. |
I'm trying to add the netbox-proxbox plugin and running into an issue. In the plugin config there is supposed to be a list of dictionaries, each dict being individual proxmox clusters. i'm just trying to test with a single cluster, so my "proxmox" list has a single dict element. However, the error i'm getting running the update.py script seems to indicate it's doing a dict.get() against the "proxmox" list() which obviously won't work.
I was able to fix this problem by eliminating the list square brackets so there's just the single dictionary defined. But this fix makes it so only one cluster can be configured, and I would like to add 3 or 4 of them when I put this into production use.
Am I doing something wrong?
Config blob from configuration.py using template config from documentation
Output from netbox update.py script
I have confirmed the below config works when running update.py, by eliminating the list brackets and having a single 'proxmox' dict element in PLUGINS_CONFIG.
The text was updated successfully, but these errors were encountered: