Spring Boot v2.1.0 stack sample doesn't show composite commands in Eclipse Che

[dmytro-ndp]

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area registry

What versions of software are you using?

Eclipse Che Next (7.85.0-SNAPSHOT) Dev Spaces 3.12.0 deployed to workspaces.openshift.com

Web browser

Operating System and version:

Browser name and version:

Bug Summary

Describe the bug:

When I created workspace using devfile https://github.com/devfile/registry/blob/main/stacks/java-springboot/2.1.0/devfile.yaml in Eclipse Che 7.85.0 / Dev Spaces 3.12.0, I saw no composite commands build-image, deployk8s in the devfile task list in VS Code editor:

  - id: build-image
    apply:
      component: build
  - id: deployk8s
    apply:
      component: deploy
  - id: deploy
    composite:
      commands:
        - build-image
        - deployk8s
      group:
        kind: deploy
        isDefault: true

To Reproduce:

1. Create and open workspace on DevSandbox using the link https://workspaces.openshift.com/#/https://raw.githubusercontent.com/devfile/registry/main/stacks/java-springboot/2.1.0/devfile.yaml
2. Go to top left menu > Terminal > Run Task...
3. Open list of devfile commands.

There are only 3 commands in the list:

• devfile: build
• devfile: run
• devfile: debug

Expected behavior

Task list includes next composite commands described in the https://github.com/devfile/registry/blob/main/stacks/java-springboot/2.1.0/devfile.yaml:

• devfile: build
• devfile: run
• devfile: debug
• devfile: build-image
• devfile: deployk8s

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Additional context

Any workaround?

Suggestion on how to fix the bug

[thepetk]

@dmytro-ndp I'm closing this issue as a "duplicate" of https://github.com/devfile/api/issues/1524.

I've been investigating the reason of the commands not showing up. I've found out that the issue is happening for all devfiles that their commands use the commands.apply field and not the commands.exec field.

Example for example you can notice the same behavior for go 2.3.0, 2.2.0 etc.