Update Devfile Samples to reference v2.2.0 Parent stacks

[kim-tsao]

Which area this feature is related to?

/area registry

Which functionality do you think we should add?

The current samples have a parent reference to the default stack version in the registry. e.g. Devfile sample go basic points to the default go stack version in the community registry. With this set up, parsing the samples will be successful because there are no conflicts. If the sample were changed to point to the latest version (v2.2.0 schema), parsing will fail because the parent and sample devfiles both contain the same command ids. We should create a new version of the devfile sample that is compatible with the parent 2.2.0 schema.

Why is this needed? Is your feature request related to a problem?

Detailed description:

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[thepetk]

@kim-tsao I'm not 100% about the workaround for this issue. In my mind I have two options:

1. Create a dir inside the sample repo and have different versions of devfiles (like we do in the registry)
2. Create a new branch that will host the new devfile which will point to the latest version of go stack)

[kim-tsao]

@kim-tsao I'm not 100% about the workaround for this issue. In my mind I have two options:

1. Create a dir inside the sample repo and have different versions of devfiles (like we do in the registry)

2. Create a new branch that will host the new devfile which will point to the latest version of go stack)

@thepetk I had to verify if the extraDevfileEntries.yaml has multi-version support and it looks like it does: https://github.com/devfile/registry-support/blob/main/index/generator/tests/registry/extraDevfileEntries.yaml#L11-L23

We can set up the samples similar to the test registry nodejs sample , so option 1 is preferred but we need to see if the viewer can process samples like stacks where default versions can be specified like this example here: https://github.com/devfile/registry/blob/main/stacks/nodejs/stack.yaml

[thepetk]

Moving to next sprint (239) as we need to put it on hold for now.

[thepetk]

Resumed working on the issue.

[thepetk]

Working locally in order to check if the registry viewer supports sample versioning

[thepetk]

I've tried to check if the viewer supports multiple versions for samples:

• Created a new image locally for registry having the nodejs sample with two versions:

versions:
  - version: 1.0.0
    schemaVersion: 2.0.0
    description: nodejs with devfile v2.0.0
    git:
      remotes:
        origin: https://github.com/redhat-developer/devfile-sample
  - version: 1.0.1
    schemaVersion: 2.2.1
    default: true
    description: nodejs with devfile v2.2.0
    git:
      remotes:
        origin: https://github.com/nodeshift-starters/devfile-sample

• I've built the image and deploy it on local minikube cluster but I wasn't able to see the 2 different versions of the sample in the UI.

Should we consider adding a feature in the viewer or am I missing something?