The SQL query to filter hosts on sensitive networks was incorrect
because of the join on Interfaces. There can be several interfaces per
host.
DISTINCT added to return only the proper number of hosts.

JIRA INFRA-1888 #action In Progress

This is for admin only.
Note that deleting a network with existing hosts is not allowed.
Same for domain, network scope...
Will make testing csentry-api easier by allowing to reset the db during
tests.

JIRA INFRA-1853 #action In Progress

If not given, the IP is allocated automatically (first available).
This is how it works when using the web UI.

JIRA INFRA-1833 #action In Progress

JIRA INFRA-1724 #action In Progress

Sensitive hosts shall not be returned in search and get queries (both
web and API) for non admin users

JIRA INFRA-1671

JIRA INFRA-1671

JIRA INFRA-1671 #action In Progress

Endpoints required to update host and interface via the API

JIRA INFRA-1406 #action In Progress

JIRA INFRA-931 #action In Progress

Tags were basically only used for IOCs.
Tags were linked to the interface (and not the host).
But for IOC we assume it should always be the main (first) interface.

Using a field on the host table will make it more obvious for users.

Created a IOC dynamic group type, to create a group including all IOCs

JIRA INFRA-862 #action In Progress

Allow to specify the gateway for each network

JIRA INFRA-809

Mac table removed from Network part (mac is saved as a column in the
Interface table).

JIRA INFRA-674 #action In Progress

JIRA INFRA-578 #action In Progress

JIRA INFRA-578

- Host names are unique (no 2 hosts with same name)
- A host name shall not conflict with a cname or interface (if not main
interface)
- Interface names are unique (no 2 interfaces with same name)
- An interface shall not conflict with a cname or host (if not assigned
host)
- cnames are only unique by domain (2 cnames can have the same name if
different domains)
- A cname shall not conflict with a host or interface
- An interface has to be linked to a host

Validation is implemented at the model level.
Some is also implemented at the form level as it gives nicer feedback,
but not all as it's a bit more complex when it requires check on several fields.

JIRA INFRA-245

- mac is now a column in the interface table (no link to the mac table)
- mac column is unique (can't have 2 interfaces with the same mac)
- the mac table is kept for the items

JIRA INFRA-639

Add endpoints:
DELETE /network/hosts/<host_id>
DELETE /network/interfaces/<interface_id>

JIRA INFRA-570 #action In Progress

Using flask-login request_loader, we can validate jwt tokens.
This allows to use the same decorators for the web UI (using cookies)
and the API (using JWT) as well as the current_user local proxy.

JIRA INFRA-424

- add ansible_groups_hosts_table for many-to-many relationship between
groups and hosts
- add new api endpoint /network/groups

JIRA INFRA-412

https://black.readthedocs.io/en/stable/

1. When we have a stack of switches, the same IP is associated to several
   switches
2. Move the items <-> host assocation to the item create/edit page

JIRA INFRA-267

JIRA INFRA-281

"type" field on host replaced with foreign key "machine_type_id"

JIRA INFRA-281

Allow to filter by domains

- add domain_id on NetworkScope table to define a default domain
- add domain_id on Network (default to the Network Scope one)

Fixes INFRA-194

The string representation of a Network is the vlan_name.
This is what we should allow to pass as string to create an interface.

Note that if we pass network_id instead of network when creating
and interface, the validate_interfaces method from the Network class
is not called.

Pagination information (next, prev, first, last) is included in the Link
HTTP header.
The total number of entries is provided in the X-Total-Count HTTP
header.

Split API in different blueprints like for the web UI:
- users (login)
- inventory
- network

Use version in API url (api/v1) to make future changes easier without
breaking backward compatibility