Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
We've been investigating a two component approach:
The scanner is responsible for determining if a new
The checker is responsible for running any checks (and type checks) that get added to the database. The check will scan the table and grab a lock to run the check. If it can't get the lock it will simply retry next time it runs. The checker should run regardless of any preconditions that the scanner might care about.
Any requests made to the
While working through this issue we've hit a bit of a wrinkle.
Ever since we introduced global resources, radar's behaviour has been a bit strange. Basically every
In the context of our two component system (outlined above), the
This lead us down the path of refactoring the exec package so that we can add a
Notes from IPM regarding the handling of missing versions for parent resource types:
Also: be sure to not surface 'orange boxes' for missing resource type versions - just show a special message in the UI, since we expect this state to happen when a resource is first configured.
Hey @pivotal-jamie-klassen , did UX end up creating an issue for performing the necessary changes to the UI regarding getting the status from the specific
(i.e., use the
Asking that because we just saw the effects of not having that implemented
Some observations after deploying 5.6 with Lidar on our internal supported concourse env wings.