soyuz upload policy engine needs simplification
Bug #30983 reported by
Daniel Silverstone
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The upload policy engine currently makes a vast number of decisions, some of which are non-trivial.
The code is, as a result, quite complex in places. This needs simplifying so that when we move the policy storage into the database we don't end up with even more scary code.
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| Changed in qprocd: | |
| assignee: | nobody → cprov |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Celso Providelo (cprov) wrote | #2 |
Revision history for this message
| Celso Providelo (cprov) wrote | #3 |
| Changed in soyuz: | |
| importance: | High → Medium |
| Changed in soyuz: | |
| assignee: | Celso Providelo (cprov) → nobody |
| tags: | added: tech-debt |
| Changed in launchpad: | |
| importance: | Medium → Low |
| summary: |
- upload policy engine needs simplification + soyuz upload policy engine needs simplification |
To post a comment you must log in.
Indeed, even if 'simplification' makes this task so vague ;) We do need proper model for upload policy which should include persistent storage and zope integration.