From b11d31ef23c5dfee6bfa54afbec47fc8b8bab7b1 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Sun, 13 May 2018 15:30:23 +0300 Subject: Change: how controller stores persistent data Replace old State class with new FilePersistentState and TransactionalState classes. Use new Resource class instead of raw dicts. Use context managers for creating, updating resources, to avoid mistakes from accidentally not saving changes. Overall persistence should now be rather simpler. This should open up a possibility for changing the controller to insert more actions into the build graph, to trigger notifcations via the workers. --- yarns/600-unauthz.yarn | 9 --------- 1 file changed, 9 deletions(-) (limited to 'yarns/600-unauthz.yarn') diff --git a/yarns/600-unauthz.yarn b/yarns/600-unauthz.yarn index 55cac30..c656f0e 100644 --- a/yarns/600-unauthz.yarn +++ b/yarns/600-unauthz.yarn @@ -62,11 +62,6 @@ Set up the controller. ... with an invalid token and body {} THEN result has status code 401 - WHEN outsider makes request - ... GET /projects/rome/status - ... with an invalid token - THEN result has status code 401 - WHEN outsider makes request GET /builds with an invalid token THEN result has status code 401 @@ -74,10 +69,6 @@ Set up the controller. ... POST /workers with an invalid token and body [} THEN result has status code 401 - WHEN outsider makes request - ... PUT /projects/rome/status with an invalid token - THEN result has status code 401 - WHEN outsider makes request ... GET /work with an invalid token THEN result has status code 401 -- cgit v1.2.1