Markku Leiniö

Yeah and to be extra clear for other readers, I'm suggesting accepting both `str` and `pathlib.Path` (in type hint something like `Union[str, pathlib.Path]`).

I'm confused: Why is `models` named "models" even though it is all about apps? I'm not Django-fluent so I may have misunderstood something 😄 Anyway, this `register_model()` approach seems interesting....

Btw about OpenAPI: > Using the openapi spec's been brought up before In NetBox 3.0.5 an internal cache was added in https://github.com/netbox-community/netbox/commit/257c0afdb5b62c7ea84159d2b46d53ce5a43f3a3 so now only the first `/api/docs/?format=openapi` call is...

... except that I forgot that NetBox 3.2 will not run with Python 3.7, so some other refactoring in the GitHub workflow will be needed as well. All checks were...

Your idea of separating the tests sounds good to me: unit tests should catch any apparent problems with different Python versions, and integration tests should ensure compatibility with different NetBox...

@raddessi feel free to open another PR for the above (I'm not sure off the bat how to achieve it), I can very well close this one at that point.

For me it looks like the correct solution is to configure the reverse proxy correctly (because as you said, the incorrect URL is in the data returned in your NetBox...

Please provide a minimum reproducable example of the situation (what did you try to do with what kind of input etc), that will hugely help someone to start tackling the...

How exactly is this related to `pynetbox` package?

Are you able to do the same in NetBox GUI? I'm asking because the error text is not from `pynetbox`, it is coming from NetBox API.