Rahuλ Dé

@aldosolorzano I think this makes sense. We can create a reference service like the artifact store and the resource provider which runs alongside the Bob cluster and listens for webhooks...

Essentially the intention here is to come up with a comprehensive map of what the state the cluster is in currently. Could be similar to what Elasticsearch [provides](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-state.html) for instance....

Maybe the stats can be avoided now that the metrics [API](https://github.com/bob-cd/bob/blob/main/apiserver/src/apiserver/metrics.clj) is there.

> is there a way to ask for a health endpoint? We do have a health check [endpoint](https://bob-cd.github.io/pages/api-reference.html#operation/HealthCheck). In addition to that Bob runs a periodic [heartbeat](https://github.com/bob-cd/bob/blob/main/apiserver/src/apiserver/healthcheck.clj#L59) that can warn...

When looking at the source, I do see the complexity in implementing this. I believe we need to do a merge of `%` and `default-project-specs` [here](https://github.com/clojure-lsp/clojure-lsp/blob/master/lib/src/clojure_lsp/startup.clj#L185). But the merge needs...

I was thinking the merge could check for `"deps.edn"` as a substring match in the ones provided by the user and if that matches, we inject the default `:classpath-cmd` maybe?

Yes, I would second a better and cleaner implementation deprecating this one. I suppose the config being a vec of maps is to have some form of priority? Would be...

`:classpath-discovery` seems better and then I think we can use `:cmd` instead of `:classpath-cmd`. Merging this map with the `:project-specs` vector is still a bit complex I think. But in...

Makes sense!

Thanks a lot! I tried parsing this [spec](https://github.com/bob-cd/bob/blob/main/apiserver/resources/bob/api.yaml) with this code with my limited understanding: ```clojure (-> "api.yaml" (slurp) (clj-yaml.core/parse-string) (martian.openapi/openapi->handlers {})) ``` But I still see the refs in...