uck9

Updating the code to permit the installation based on version number plus some edits in the templates does permit this plugin to work in 3.0 and 3.1. Been running a...

If anyone's interested, I've done a quick and dirty fixup of the current code to support (at least on my install) Netbox 3.4. 99% of the fixups were in the...

Two changes are needed at least in the sync_eox_data script: Update following line: token_url = "https://id.cisco.com/oauth2/default/v1/token" Update the 'url' line to have a fqdn of 'apix.cisco.com' instead of 'api.cisco.com'. Eg...

OK, issue with the SSL NEG error has to be fixed in the netbox_docker image. Not got a scripted workaround but if you add: Options = UnsafeLegacyRenegotiation to the section...

I'd second this. There's some overlap here with design included on the NetBox Lifecycle plugin but my thoughts are that it's better associating the support contracts with the asset records...

There’s actually a good set of models around support contracts in Dan Sheps netbox-lifecycle plugin. I’ve been working through the idea of a seperate support contract plugin to this inventory...

@shepherdjay - Yeah Dan's done some good work on the contracts model. Thoughts from experience with Cisco Contracts: - A Contract exists that's associated with a vendor and has a...

On the contracts item I’ve probably done a bad job of explaining the layout. Isn’t hierarchical contracts, just more the fact that every device attached to a contract can have...

Agreed on keeping this seperate to any discussions around support contracts. Suggesting to add a hardware warranty type to the current model to better track the actual type of hardware...