The current way the recipe is written does not allow much flexibility for an installation using a remote database server. For example, if the gitlab application server does not have access to login to the database as root to setup the gitlab account and database or the administrator would choose not to for security purposes. Allowing the ability to disable the setup of the database with the attribute allows for the database to be configured on a different server.
Specifying the certificate databag type with an attribute would allow for usage with chef-vault. The default type is encrypted which is the default from the certificate cookbook.
The current way the recipe is written does not allow much flexibility for an installation using a remote database server. For example, if the gitlab application server does not have access to login to the database as root to setup the gitlab account and database or the administrator would choose not to for security purposes. Allowing the ability to disable the setup of the database with the attribute allows for the database to be configured on a different server.
Specifying the certificate databag type with an attribute would allow for usage with chef-vault. The default type is encrypted which is the default from the certificate cookbook.