Helloasso to Discourse
This works in two distinct steps: first fetch HelloAsso data, then sync with Discourse.
Installing
pip install .
Using
1 — Choose what to sync
The goal is to sync an HelloAsso event (they call it forms) to a Discourse Badge.
First let's discover which HelloAsso 'forms' we can use:
$ helloasso-to-discourse list-forms --ha-client-id="$(pass helloasso-clientid)" --ha-client-secret="$(pass helloasso-clientsecret)" --ha-org=afpy
Then let's discover which Discourse badges we can use:
$ helloasso-to-discourse list-badges --discourse-url=https://discuss.afpy.org --discourse-api-key="$(pass afpy/discuss.afpy.org-api-key)"
2 — Sync
This step actually assigns badges to Discourse users:
As an example to assign badge "membre" to HelloAsso users having paid for the form named adhesion-2023-a-l-afpy:
$ helloasso-to-discourse sync --ha-client-id="$(pass helloasso-clientid)" --ha-client-secret="$(pass helloasso-clientsecret)" --ha-org=afpy --discourse-url=https://discuss.afpy.org --discourse-api-key="$(pass afpy/discuss.afpy.org-api-key)" --ha-form adhesion-2024-a-l-afpy --discourse-badge adherant-afpy
And an example to assign Discourse badge pyconfr-2023 to members having registered for the pyconfr-2023 event on HelloAsso:
$ helloasso-to-discourse sync --ha-client-id="$(pass helloasso-clientid)" --ha-client-secret="$(pass helloasso-clientsecret)" --ha-org=afpy --discourse-url=https://discuss.afpy.org --discourse-api-key="$(pass afpy/discuss.afpy.org-api-key)" --ha-form pyconfr-2023 --discourse-badge pyconfr-2023
$ helloasso-to-discourse sync --ha-client-id="$(pass helloasso-clientid)" --ha-client-secret="$(pass helloasso-clientsecret)" --ha-org=afpy --discourse-url=https://discuss.afpy.org --discourse-api-key="$(pass afpy/discuss.afpy.org-api-key)" --ha-form pyconfr-2024 --discourse-badge pyconfr-2024
Metadata
Release files for helloasso-to-discourse 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| helloasso_to_discourse-0.4.tar.gz | 4.9 kB | Without provenance | Details for helloasso_to_discourse-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| helloasso_to_discourse-0.4-py3-none-any.whl | Python 3 | none | any | Details for helloasso_to_discourse-0.4-py3-none-any.whl |
Total release size: 10.3 kB
Release files / helloasso_to_discourse-0.4.tar.gz
| Download URL | helloasso_to_discourse-0.4.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb5ab3e59e7fc3758ca19f2ca195b885a693036d3ef3fa7ee1aeb2ce261e1a5a
|
|
BLAKE2b-256 checksum How to use checksums |
a83c8dc6fd589e708497191a6fec0a043f7fb732f7baa3a0cbb427bf7f84d0a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / helloasso_to_discourse-0.4-py3-none-any.whl
| Download URL | helloasso_to_discourse-0.4-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4a7af71ba38386d44f13e0797ed6452a927118869a03182c094a3e1c3f82b56
|
|
BLAKE2b-256 checksum How to use checksums |
9cefe09f9434aa299649d0499372707636af0acb78d096a22ac64a63be967150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for helloasso-to-discourse 0.4
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.