[IMP] core: allow auto_install restriction on a subset of dependencies

Currently, auto_install is triggered when all dependencies get
installed, but there are cases where one would want such trigger on
only a subset thereof.

e.g. we want `website_sale_dashboard` to auto-install when
`website_sale` is installed. Currently, it requires `web_dashboard` to
also be auto-installed otherwise `website_sale_dashboard` would "wait"
for both dependencies to be explicitly installed before the
auto-install triggers. That's despite `web_dashboard` not being very
useful on its own. More generally this is an issue with technical
modules which need to be marked as auto_install so as not to block
e.g. bridge modules from automatically installing.

This change allows setting `auto_install` to a subset of `depends`:

* if auto_install is set to `False`, the module does not get
automatically installed (no change in semantics)
* if auto_install is set to `True`, the module gets automatically
installed if and only if all its dependencies are installed (also no
change in semantics)
* if auto_install is set to a list of dependencies, the module will be
installed when all *these* dependencies are installed, other
dependencies (excluded from auto_install) will be installed
alongside as a consequence
* auto_install can be set to an empty list, in this case the module
will always be automatically installed regardless of its
dependencies (and will force their installation).

So after this change, `web_dashboard`'s auto_install can be set to
`False` (such that it's not installed if no module defining dashboards
is installed) and `website_sale_dashboard`'s manifest can be edited
to:

'auto_install': ['website_sale']

possibilities:

# no automatic installation
'depends': ['a', 'b'],
'auto_install': False

# automatic installation if both a and b are installed
'depends': ['a', 'b'],
'auto_install': True

# automatic installation if both a and b are installed (explicit)
'depends': ['a', 'b'],
'auto_install': ['a', 'b']

# automatic installation if b is installed, a will get forcefully
# installed if it isn't yet
'depends': ['a', 'b'],
'auto_install': ['b']

# always automatically installed, will cause the installation of
# its dependencies even if they're not marked explicitly
'depends': ['a', 'b'],
'auto_install': []

Task 1851328

closes odoo/odoo#29431

Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>

1 files changed, 16 insertions, 1 deletions

diff --git a/odoo/modules/loading.py b/odoo/modules/loading.py
index 5fb56887948..6b924f09bf4 100644
--- a/odoo/modules/loading.py
+++ b/odoo/modules/loading.py
@@ -379,7 +379,22 @@ def load_modules(db, force_demo=False, status=None, update_module=False):
 
             _check_module_names(cr, itertools.chain(tools.config['init'], tools.config['update']))
 
-            module_names = [k for k, v in tools.config['init'].items() if v]
+            # auto-install module second pass: recursive bit in db.py handles
+            # auto_install modules with no dependencies or where all
+            # dependencies are auto_install, couldn't get it to work with
+            # non-required auto_install deps so here
+            cr.execute("""
+            SELECT m.name FROM ir_module_module m
+            WHERE m.auto_install
+            AND m.state != 'installed'
+            AND NOT EXISTS (
+                SELECT 1 FROM ir_module_module_dependency d
+                JOIN ir_module_module mdep ON (d.name = mdep.name)
+                WHERE d.module_id = m.id
+                  AND d.auto_install_required
+                  AND mdep.state NOT IN ('installed', 'to install')
+            )""")
+            module_names = [k for k, v in tools.config['init'].items() if v] + [x[0] for x in cr.fetchall()]
             if module_names:
                 modules = Module.search([('state', '=', 'uninstalled'), ('name', 'in', module_names)])
                 if modules: