Carrier accounts configuration with server_environment
This module allows to configure carrier informations using the server_environment mechanism: you can then have different servers for the production and the test environment.
Table of contents
Configuration
With this module installed, the delivery carrier are configured in the server_environment_files module (which is a module you should provide, see the documentation of server_environment for more information).
In the configuration file of each environment, you may first use the section [carrier_account].
Then for each server, you can define additional values or override the default values with a section named [carrier_account.resource_name] where “resource_name” is the name of the server.
Example of config file :
[carrier_account] # here is the default format file_format = 'ZPL' [carrier_account.mycarrier] name = mycarrier account = 587 password = 123promenons-nous-dans-les-bois456cueillir-des-saucisses [carrier_account.mycarrier2] name = mycarrier2 account = 666 password = wazaaaaa file_format = PDF
As an alternative of server_environment_files, there is also a module named server_environment_data_encryption which allow to set the environement dependent values directly in the database, by the user itself. It will be encrypted, to avoid security issues with secrets, see the documentationn of server_environment_data_encryption for more information. The advantage of setting the environment dependent value directly in the database is that it does not require a developper/odoo administrator to change a carrier account.
Usage
Once configured, Odoo will read the carrier values from the configuration file related to each environment defined in the main Odoo file or in carrier.account model.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
David Béal <david.beal@akretion.com>
Guewen Baconnier <guewen.baconnier@camptocamp.com>
-
Bhavesh Heliconia
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/delivery-carrier project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-carrier-account-environment 18.0.1.0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_carrier_account_environment-18.0.1.0.0.3-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_carrier_account_environment-18.0.1.0.0.3-py3-none-any.whl |
Release files / odoo_addon_carrier_account_environment-18.0.1.0.0.3-py3-none-any.whl
| Download URL | odoo_addon_carrier_account_environment-18.0.1.0.0.3-py3-none-any.whl |
|---|---|
| Size | 28.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eec828defc129329aa2d9d74b50f03308ca0ebab60c5c9bc7936741ef362e9e7
|
|
BLAKE2b-256 checksum How to use checksums |
6d18acbb205953e45bec4647e70475a3bf270ffd2ea36dc91d5862a368433cd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-carrier-account-environment 18.0.1.0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.