Validation worked in the models because fullmatch is used but in the
Regexp validators from wtforms, only match is called.

The form validator didn't catch "AAA1100".
Test added for this.

JIRA INFRA-1569 #action In Progress

A string or list is valid YAML but not valid for Ansible variables.
We expect only key-value-pairs (dict).

JIRA INFRA-1221

Replace previous implementation based on the domain.

The domain can be changed per network but in practice we always use the
same domain in a network scope.
We currently have 9 network scopes but only 3 domains.
Using the network scope gives us finer granularity in practice.

JIRA INFRA-1228 #action In Progress

JIRA INFRA-1049 #action In Progress

- admin can delete any hosts
- normal users can delete hosts they created

Note that still only admin users can delete hosts via the API (more dangerous
operation as a script could delete many hosts).

JIRA INFRA-1018 #action In Progress

- users with access to the network can create VIOC
- VM can be created only in the ALLOWED_VM_CREATION_DOMAINS

JIRA INFRA-775

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

The MAC field has both a Regexp and Unique validators.
In wtforms, the validation doesn't stop on the first error (all
validators are run).
In case of invalid mac address, the Unique validator makes a request to
the database that raises a DataError. This exception has to be catched.

JIRA INFRA-777 #action In Progress

Search on keyword can be made case insensitive by using a normalizer.
But some fields with type keyword include several words.
They are only returned by entering all words. This is not what
most users expect.

It's better to use the "text" type by default (for text fields) and add
an extra "keyword" field of type "keyword" for sorting.

JIRA INFRA-770

JIRA INFRA-763

Not sure why a tuple instead of network was returned...
There must have been a comma at the end of the line due to copy/pasting
and black converted that to a tuple.

Added a test for the create_interface function.

JIRA INFRA-697 #action In Progress

- create_host doesn't return 403 for user_lab but 200 because the form
  validation fails (the network_id is not part of the form choices)
- caching disabled during tests
  the current_user could sometimes return a different username because of
  caching: the database is cleaned between each test, so different users
  can have the same id and an old user could be returned instead of the new
  one due to caching

JIRA INFRA-578

- 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

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

JIRA INFRA-618 #action In Progress

- switch to server side processing to retrieve network hosts
  (the table started to be bigger and takes time to load)
- add full text search using elasticsearch

Note that only the first IP is displayed in the host table (all
interfaces were displayed before). Search can be performed on any
interfaces.

JIRA INFRA-595 #action In Progress

JIRA INFRA-575 #action In Progress

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

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

Fixes INFRA-197

Allow to keep track of batches of small parts.

Column not visible but searchable.
Allow to search comments and TAG number for items imported from JIRA.

Required to create users when importing items from JIRA.

Renamed blueprint from "users" to "user" to be consistent with other
blueprints (inventory and network).

+ fix tests

Put under the functional directory all tests that require
access to the database. There is a "session" fixture in that
directory that is automatically invoked for each tests. It rollbacks
any transaction after the test to leave the database clean.

Other tests should go under the unit directory.

Inspired from:
- https://stackoverflow.com/a/38626139
- http://alexmic.net/flask-sqlalchemy-pytest/