View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009984 | Taler | exchange | public | 2025-05-20 01:16 | 2026-11-03 13:37 |
| Reporter | Florian Dold | Assigned To | Resolution deadline | ||
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | low | Severity | feature | Reproducibility | have not tried |
| Status | acknowledged | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0009984: consider better mechanism to configure AML helpers | ||||
| Description | Right now, we have these choices: * hardcode config in AML programs => bad configurability/flexibility * read Taler config on every run => bad performance * read via environment variables => difficult to test, confusing Instead, maybe the AML helper should (via some introspection flag) tell the exchange which configuration values it needs (section, option, type (number, string, boolean, file path)). | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-20 01:16 | Florian Dold | New Issue | |
| 2025-05-20 19:54 | Christian Grothoff | Status | new => acknowledged |
| 2026-08-29 17:02 | Florian Dold | Target Version | post-2.0 => 1.7 |
| 2026-11-03 13:37 | Christian Grothoff | Target Version | 1.7 => post-1.0 |