maziggy 732b1d7034 fix(backup): gate every restore category on the permission owning its rows (#2656) ...

settings was gated on settings:update because a restore rewrites rows
    PUT /api/v1/settings/ owns. The same argument applies to the other three
    categories, and gating one but not the rest is the only state that is
    not defensible: a role holding Backup alone could still write spools,
    archives and K-profiles through a restore that it cannot write through
    the endpoints that own them.

    Each category now also requires that endpoint's write permission -
    inventory:update, archives:update_all and kprofiles:update. archives
    takes update_all rather than create because a restore writes rows owned
    by other users, which is exactly what update_all means.

    All missing permissions are reported in one refusal: a restore is a
    multi-select, so naming them one at a time turns picking four categories
    into four round trips.

2026-08-15 14:25:46 +02:00

..

_fixtures

…

integration

fix(backup): gate every restore category on the permission owning its rows (#2656)

2026-08-15 14:25:46 +02:00

unit

docs(backup): say what the secret-key hints actually refuse (#2656)

2026-08-15 14:25:31 +02:00

__init__.py

…

conftest.py

feat(projects): per-file print progress and complete-sets tracking (#1897)

2026-07-28 12:46:31 +02:00

pytest.ini

test(pytest): silence upstream starlette httpx2 deprecation noise

2026-05-30 14:19:19 +02:00