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

- add term coverage report to capture it in gitlab-ci
- add pipeline and coverage badges

There are no local user. This wasn't used.

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

The device_type has an impact on the DHCP configuration.

JIRA INFRA-1846 #action In Progress

- Allow to use "-" in device type name
- Add ALLOWED_SET_BOOT_PROFILE_DEVICE_TYPES variable
- Rename MicroTCA to MTCA-AMC

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

The repository was created for IOC Factory but this isn't used.
Repo should be created by IOC Factory anyway if required.

JIRA INFRA-1839

This is a dynamic group which will include all hosts that start with the
same name as the group

JIRA INFRA-1844 #action In Progress

Normal users can only view networks they have access to

JIRA INFRA-1809 #action In Progress

The trigger functions were refactored but job_template was passed
instead of inventory_source.

JIRA INFRA-1792 #action In Progress

JIRA INFRA-1790 #action In Progress

JIRA INFRA-1788 #action In Progress

The version file is created when building the docker image
using the git tag.

Switch to calendar versioning

JIRA INFRA-1789 #action In Progress

Add default command as well

- Remove "- CSEntry" (logo is already displayed in tabs depending on the
  browser)
- Specify name of the instance in view and edit pages

JIRA INFRA-1726 #action In Progress

JIRA INFRA-1724

JIRA INFRA-1724 #action In Progress

make test should use "-f docker-compose.yml" to not mount the postgres
data volume
See b4f9c100

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-1669 #action In Progress

JIRA INFRA-1660 #action In Progress

JIRA INFRA-1627

JIRA INFRA-1627 #action In Progress

Check that a group child is not:
- the group itself
- the "all" group
- in one of the parent groups (recursively)

JIRA INFRA-1622 #action In Progress

stack_member was incorrectly coerced to a string

JIRA INFRA-1648 #action In Progress

Using a volume for postgres data makes the tests very slow on OSX.
When running the tests, there is no need to persist the data (db is
recreated before each session).

`make db_test` should be used to start postgres without mounting the data
volume (skip the docker-compose.override.yml).

JIRA INFRA-1604 #action In Progress