Private Key Configuration in l10n_fr_account_vat_return_teledec

[zuher83]

Description: In the README of the l10n_fr_account_vat_return_teledec module for Odoo, the module's @alexis-via recommends adding a teledec_private_key entry to the Odoo Server configuration file, using the private key provided by Teledec.

However, a problem arises when multiple databases are hosted on the same server, as each database requires its own private key. Storing the key in the Server configuration file makes it global, which can lead to conflicts.

Proposed Solution:

• Consider storing the private key in res.company to make it specific to each company.
• Address the issue of multi-company environments to ensure proper key management.

Implementing this change would enhance the module's usability in scenarios where multiple databases exist on the same server or in multi-company environments.

Is there a specific reason for the key to be in the config file that I may not have considered?

[alexis-via]

You'd better use the same teledec private key for several companies, to benefit from the volume discounts of teledec. I did that on purpose.

[github-actions[bot]]

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.