Stacks/Devfile matching rules

[elsony]

In a devfile that is being used to define a stack, there are certain files that the stack may be looking for to decide if a given project can be run by a given stack or not, e.g. a maven stack may look for the pom.xml and a node.js stack may look for package.json.

If we can provide a way to allow a given stack to define those required resources, we can use it in tools like Che or odo to do quick check on project to suggest the stacks on a devfile repo that may support the a given application. An example can be:

parent.yaml
---
schemaVersion: 2.0.0
metadata:
  publisher: my-org
  name: maven-stack
  version: x.y.z
  matchingRules:
    existingFiles: ['pom.xml', 'aaa.xml']

devfile.yaml
---
schemaVersion: 2.0.0
metadata:
  name: my-maven-project
parent:
  id: organization/maven-stack/x.y.z
...

There may be other types other than existingFiles that we can support in the future.

[l0rd]

Reviewed and agreed

[davidfestal]

We will have to think about how we do the same for a parent existing as a Kubernetes resource (DevWorkspaceTemplate). We might want to use K8S metadata int his case, but then let's keep in mind that K8S metadata are simply a map of strings, while here the matching rules define a structured sub-schema. I assume we don't want to split the related syntax and have 2 different ways to express that between yaml parent devfiles and K8S CRD parents devfiles.

[davidfestal]

If that's a structured information that is valid for both the devfile Yaml and the devworkspace template CRD, I'd rather have a true field for it.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.