This release is a pre-release and may not be stable for production use.
Server environment for JIRA Connector
This module is based on the server_environment module to use files for configuration. Thus we can have a different configuration for each environment (dev, test, integration, prod). This module define the config variables for the connector_jira module.
In the configuration file, you can configure the location, enable/disable the SSL and the webhook base url of the JIRA Backends.
Exemple of the section to put in the configuration file:
[jira_backend.name_of_the_backend] uri = http://jira verify_ssl = 1 odoo_webhook_base_url = http://odoo:8069
1 maintainer
Metadata
1 maintainer
Release files for odoo11-addon-server-env-connector-jira 11.0.1.0.0.99.dev4
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 |
|---|---|---|---|---|
| odoo11_addon_server_env_connector_jira-11.0.1.0.0.99.dev4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for odoo11_addon_server_env_connector_jira-11.0.1.0.0.99.dev4-py2.py3-none-any.whl |
Release files / odoo11_addon_server_env_connector_jira-11.0.1.0.0.99.dev4-py2.py3-none-any.whl
| Download URL | odoo11_addon_server_env_connector_jira-11.0.1.0.0.99.dev4-py2.py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c83531f561c9f107d02c9e4fa62f6bb2e249da1abe3dc7429f149a5e5643eeae
|
|
BLAKE2b-256 checksum How to use checksums |
c45d30fbd80dad17128bc66fbd4318b0c856a9a7a5ffbd33b6ad49d5baf1afd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo11-addon-server-env-connector-jira 11.0.1.0.0.99.dev4
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.
