View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010174 | Taler | deployment and operations | public | 2025-07-09 17:15 | 2025-07-09 17:15 |
| Reporter | Christian Grothoff | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.0 stretch goals | ||||
| Summary | 0010174: ansible script to import new sanction list is dated, needs to be improved | ||||
| Description | It should stop taler-exchange-sanctionlist, run taler-exchange-sanctionlist -r -n and then re-start the service. Instead it uses some legacy invocation to upload the latest list, which is already done in the exchange role. Florian also wanted this all done via a special user, and not via Ansible. Tricky bit: we need to make sure that on a fresh deployment, we do install the latest sanctionlist (which is currently in the Ansible git). So not sure what the perfect process here would be like. | ||||
| Tags | compliance | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-07-09 17:15 | Christian Grothoff | New Issue | |
| 2025-07-09 17:15 | Christian Grothoff | Status | new => confirmed |
| 2025-07-09 17:15 | Christian Grothoff | Tag Attached: compliance |
