FliesLikeABrick
FliesLikeABrick
+1 I installed pynetbox from this branch and it resolved my inability to update JSON custom properties with the error cited in #457
@zachmoody can you review this? It would be great to have this fix come in upstream to fix our automation and let us avoid having to create an internal fork
You will need to script an rrd export an import that leaves the old fields behind, I do not believe I have seen a contributed script that does this
@Kani999 can you open a new PR for your fix to come back upstream to pynetbox, so that someone can hopefully review that proposed fix? I know the last one...
I am encountering this on SL with macports as well, did anyone find a workaround or fix for this?
I have a branch ready for a pull request, if this issue/request is accepted.
Hello, it has been 5 months since this was reported and I have offered a code fix - is anyone available to triage this request or provide feedback on the...
@jeremystretch thank you for the reply - we are inheriting from `Script` currently and our intermediate class is appearing in the UI alongside our two subclasses of it `class CNVRScript(Script):`
Ran into this today, opened #729 with updated URLs
If this project is actively maintained, hotkeys/shortcuts would indeed be quite valuable since the context menu has two layers of navigation/requires an extra step compared to some other extensions (which...