Ciro S. Costa

> _Expected behaviour: I would expect some sort of validation when adding new workloads or at least information about collisions._ makes sense to me! agree that it's a good validation...

Hey @odinnordico , thanks for reporting! I was trying to gather some more context here, and end up looking at what knative is making use of for that check -...

heey I was playing around with it, but found a little weird behavior - sometimes it seems to select the right DAG path, but sometimes it doesn't, not sure why....

nice! another little one - I noticed that the supplychain resource list I put above would actually not work when running a setup with the admission webhooks running e.g., with...

> _If an object does not have a spec field, there will be a cache miss when Carto examines the object. This will cause a new object to be stamped...

from what I recall, there were two big reasons for having a `ClusterRunTemplate`: 1. making Runnable useful on its own 2. preventing conflicting templating w/ carto's Cluster*Template 3. preventing conflicting...

left some context in https://github.com/vmware-tanzu/cartographer/pull/787#issuecomment-1089151660, but overall I do like the idea of trying to simplify Runnable with some form of inlining. For me the biggest issue I see at...

marking it as blocked as we'd like to tackle https://github.com/vmware-tanzu/cartographer/issues/815 first in order to be able to get rid of the templating at clusterruntemplate level w/ regards to selector

example use of servicebindings at build time: ```yaml apiVersion: kpack.io/v1alpha2 kind: Image metadata: name: sample-binding-with-secret spec: tag: my-registry.com/repo builder: kind: ClusterBuilder name: default source: git: url: https://github.com/buildpack/sample-java-app.git revision: 0eccc6c2f01d9f055087ebbf03526ed0623e014a build:...

marking as blocked as we'd like to tackle https://github.com/vmware-tanzu/cartographer/pull/787 first