Foreman-installer 2.0 does not know about "--foreman-db-type"

Problem:
Installing with an external postgresql-server as adviced within the 2.0 manual:

foreman-installer \
  --foreman-db-type=postgersql \
  --foreman-db-manage=false \
  --foreman-db-host=localhost \
  --foreman-db-database=foreman \
  --foreman-db-username=foreman \
  --foreman-db-password=foreman

gives back:

ERROR: Unrecognised option '--foreman-db-type'

Expected outcome:
foreman-installer knows about --foreman-db-type

Foreman and Proxy versions:

foreman-installer-2.0.0-1.el7.noarch
foreman-release-2.0.0-1.el7.noarch
foreman-release-scl-7-2.el7.noarch
foreman-selinux-2.0.0-1.el7.noarch
rubygem-foreman_maintain-0.6.2-1.el7.noarch

Foreman and Proxy plugin versions:

Distribution and version:

CentOS Linux release 7.7.1908 (Core)
Derived from Red Hat Enterprise Linux 7.7 (Source)

Other relevant data:
The handbook tells:

3.2.3 Installation Scenarios
The Foreman installer can accommodate more complex, multi-host setups when supplied with 
appropriate parameters.

Using an external database server
Per default foreman-installer will install a PostgreSQL database server onto the Foreman host and 
create its database. An external MySQL or PostgreSQL database server with an already created 
database can be used with the following arguments:

foreman-installer \
  --foreman-db-type=mysql \
  --foreman-db-manage=false \
  --foreman-db-host=dbserver.example.com \
  --foreman-db-database=dbname \
  --foreman-db-username=dbuser \
  --foreman-db-password=dbpassword
As a post-installation step, to populate the database correctly, run:

foreman-rake db:migrate
foreman-rake db:seed
foreman-rake apipie:cache:index

Thanks for the report. That is indeed incorrect since we no longer support multiple database types. There is only PostgreSQL support now. You can simply leave out the option and the installer will use PostgreSQL.

There are some further options not recognized:

--foreman-db-host=<host[:port]>
--foreman-db-database=<dbname>
--foreman-db-username=<dbuser>
--foreman-db-password=<dbpass>

Seems like it is impossible to tell the Installer what database it has to access and which user to take. This could be really interesting if the database is hosted on an other server.

This is incorrect usage. The host is as it says: a host. There’s --foreman-db-port for the port.

These should all still exist.