Joshua Winters

I believe those two actually target two different claims. dexidp/dex@8c1716d is the `name` claim. concourse/dex@5d302f2 is the `username` claim. The name claim is meant to be something like `Josh Winters`,...

Before we do all this work I think the main starting point would be to get upstream dex to support the `client_credentials` and `password` grant types. Because until they do...

Copying over [my comments from RFC14](https://github.com/vmware-tanzu/cartographer/pull/274#issuecomment-1010335810) that are still relevant: In the office hours this week (Jan 10th, 2022), we talked about how we could extend this type of artifact...

Copying over [my comments from RFC14](https://github.com/vmware-tanzu/cartographer/pull/274#issuecomment-1011380948) that are still relevant: @rawlingsj made a really insightful comment in another unrelated thread that we should consider here: > Customers will likely not...

@scothis > I'm in favor of capturing a reference to the resources created for a Workload on the status, but I'm skeptical that capturing the output values will give users...

Some open questions that I've heard raised: - Should workload artifacts be wiped out when spec changes? If yes, can we fast forward through the supply chain matching known inputs...

@waciumawanjohi any thoughts on this point? > Should we write an empty artifact (only has an id) when using ClusterTemplate

@scothis a lot of your comments read like "this is impossible don't even attempt this". Do you have other recommendations for how we can bring better visibility in tracing how...

In https://github.com/vmware-tanzu/cartographer/issues/774, we talked about the problem of cartographer not having any knowledge of resources it doesn't stamp out. If we were able to select extract information from arbitrary resources...

yup! It does get kinda weird though, since that `Service` may not be `Ready` (yet, or maybe ever?)