If related field is not directly set (coming from inheritance) or string
label is not specified explicitly, it might not have it in `args`,
making it generate same default field labels, causing warnings in odoo.
Before this change you could get these kind of warnings:
```
2023-09-23 13:28:39,638 1 WARNING odoodb odoo.addons.base.models.ir_model:
Two fields (field1_env_default, field2_env_default) of your.model() have
the same label: Env Default.
```
It would generate multiple fields having same label.
``odoo.fields.determine`` requires inverse methods to have ``__name__`` attribute.
Unfortunately with ``partialmethod`` this attribute is not propagated
even by using ``functools.update_wrapper``.
In any case, `update_wrapper` would propagate the wrapped func name
which is not the same here.
Introduced by 36544651f2
Add SERVER_ENV_CONFIG_SECRET alongside SERVER_ENV_CONFIG
Allows to isolate the secrets in your deployment
Improve documentation regarding variables
Add a server environment mixin
To automatically convert fields into fields reading values from the
environment. Until now, every module reimplements the same computed
field.
Read default values from database when no config is provided
Automatically add <field_name>_env_default for every field transformed
to a "computed from env" field, so a default value can be set. It will
be used when the configuration is not set in a configuration file
(when the key is absent, not empty).
Allow to edit default values for env-computed fields
When they don't have any key in the environment configuration files.
In the UI, when a field is set in a configuration file, the field is
readonly, if not the field is editable. Which means you can selectively
choose which fields depend on the environment and which can use a
"default" value stored in database.
Fix a few small issues in mixin
Use a dictionary to configure the fields
Add global section
Disable prefetch on env-computed fields
As in the inverse field that write the value into the <field>_env_default
we have to browse the record, the prefetch has the effect of calling
compute on the env-computed field which resets the value to it's
previous state before we have the occasion to store it.
Use global section name as first part of the section
Allow to edit all fields on creation
Make server_environment_files optional
Allow integration with keychain
By adding options to change the compute and inverse methods for default
fields
Update documentation of server_environment, bump
Add SERVER_ENV_CONFIG_SECRET alongside SERVER_ENV_CONFIG
Allows to isolate the secrets in your deployment
Reinforce server_environment base tests
Add tests for the server env mixin
Infer configparser getter from field type
Fixes for review feedbacks
Add tests and support of _inherits
Use SavepointCase instead of TransactionCase
It means less records to create for each test
Fix iteration on records
Andrius Laukavičius
Simone Orsi
Ivàn Todorovich
Guewen Baconnier
Adrien Peiffer
jsanchez
Mourad
Denis Roussel
Stéphane Bidoul (ACSONE)
Akim Juillerat