Jose Cortes

We are also repeatedly seeing this in concourse 5.3 We have a large number of resources that are never checked by schedules, but are often `put`. Resource history for these...

Ok i think i have some more pointers on this. We're using concourse with the kubernetes secret backend. We store our custom resource types in an internal artifact repository, and...

> Strange that rolling the web pods would affect this however. I would expect Concourse to be deterministic here; if the source configuration has changed, it's a new resource and...

FWIW we've spent the last week or so playing around with this and we can absolutely, 100% reliably reproduce this every time we rotate secrets.

@vito hmm, I'm not sure that returning everything from `check` is solving the core UX issue here 🙂 In my experience, the biggest problem with losing resource history isn't that...

> As long as the resource returns the same version, it should be equivalent and not trigger redundant builds. This is to handle the exact scenario you described. hmmm very...

Yep, we are planning on delivering #92 , which will include support for running Windows in CI -- at that point it should be easy to add tests for MacOS

cc @knlambert and @jcornick-alabs from the Telepresence team at Ambassador

Hi Dawn! Yes, we'll modify our governance per the template; I'll let you know when we've done that. Thanks!