Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Scrumban #1, Scrumban #2, Scrumban #3
Description
This may not be 100% backwards compatible, but it's the right thing to do, as right now people have to touch ideal states just to trigger a resource config change update. This is particularly relevant for the task framework, as we will be able to avoid reading the job/workflow configs repeatedly in the controller.