Remove requirement for fully-qualified domains in custom URL fields

[kopacko]

Issue type

[ ] Feature request
[x] Bug report
[ ] Documentation

Environment

• Python version:
• NetBox version: 2.1.2

Description

I created a custom field URL to point do a devices repository for configuration backups as well as to a direct REST API link from my Cisco Prime Infrastructure servers. One thing I noticed is that you have to supply a FQDN for the custom field. We have our internal domains as our search domain and I believe this field should be able to accept that form of short-hand.

For example: https://ciscoprime.domain.com (currently required)

Internally domain.com is the given search domain so https://ciscoprime (should be acceptable by this field)

I could not find any previous issues directly referencing this issue. If they exist, I apologize now.

[jeremystretch]

Validation of the URL is performed using Django's built-in URLValidator, which seems to enforce a domain name and TLD. We've already implemented our own URLField too allow for arbitrary schemes. It probably makes sense to ditch the built-in validator in favor of something more flexible.