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

JIRA INFRA-1627 #action In Progress

JIRA INFRA-1604 #action In Progress

Endpoints required to update host and interface via the API

JIRA INFRA-1406 #action In Progress

JIRA INFRA-1291 #action In Progress

Linked items are by default returned as a list of ICS id.
When recursive is True, a list of {ics_id, serial_number, stack_member}
is returned instead.

Items are always returned sorted by stack_member or ics_id when
stack_member is null.

Allow to add the serial_number and stack_member to the Ansible variables
in csentry dynamic inventory. Useful for switches.

JIRA INFRA-1111 #action In Progress

- requesting too many elements in one query has an impact on the
database and the web application
- max limit set to 100

JIRA INFRA-942 #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

Host interfaces are always returned sorted by name

JIRA INFRA-785 #action In Progress

- add fqdn to host
- add gateway to network
- add netmask to interface
- allow to pass recursive via the API (to expand interfaces in host)
- add is_main property to interface (True if the interface is the main
  interface of the host)

JIRA INFRA-640

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

- 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

New get_json method on test client response.
See http://flask.pocoo.org/docs/1.0/testing/#testing-json-apis

JIRA INFRA-424

This is not super clean. The model and device_type belong to the host.
This is for easy access from the API.
But it would be better to have a "expand=true" query parameter and return the
host as a dict.

JIRA INFRA-414

JIRA INFRA-414

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

JIRA INFRA-412

Allow to enter Ansible variables on host in YAML format.
Use codemirror (http://codemirror.net) to make editing YAML easier.

JIRA INFRA-412

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

- rename physical to physical machine
- IOC should be a tag

JIRA INFRA-302

This is to be used for stack of switches only

- a stack_member is linked to an host (device_type has to be "Switch")
- a stack_member is an integer between 0 and 9 (included) or can be None
- the couple (host_id, stack_member) must be unique

JIRA INFRA-267

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

JIRA INFRA-277

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

JIRA INFRA-281

cnames entered in CSEntry are just names not FQDN
See d1f500238c5798259f536bb80fa93aba2d493b97