Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devfile component names are not present in 'odo catalog list components' output #3827

Closed
dgolovin opened this issue Aug 24, 2020 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@dgolovin
Copy link
Contributor

/kind bug

What versions of software are you using?

Operating System: Windows 10

Output of odo version: 2.0.0-alpha2

How did you run odo exactly?

odo catalog list components

Actual behavior

C:\Users\u>odo.exe catalog list components
Odo Devfile Components:
NAME     DESCRIPTION                                                                                                                                                                     REGISTRY
         Upstream Maven and OpenJDK 11                                                                                                                                                   DefaultDevfileRegistry
         Stack with NodeJS 10                                                                                                                                                            DefaultDevfileRegistry
         Open Liberty microservice in Java                                                                                                                                               DefaultDevfileRegistry
         Spring Boot® using Java                                                                                                                                                         DefaultDevfileRegistry
         Upstream Quarkus with Java+GraalVM                                                                                                                                              DefaultDevfileRegistry
         Stack for developing NodeJS Angular Web Application                                                                                                                             CheDevfileRegistry
         Stack with tooling ready to develop Integration projects with Apache Camel K                                                                                                    CheDevfileRegistry
         Stack with environment ready to develop Integration projects with Apache Camel based on Spring Boot.                                                                            CheDevfileRegistry
         Che4z Mainframe Basic Stack is an all-in-one
C:\Users\u>odo.exe catalog list components -o json
{
        "kind": "List",
        "apiVersion": "odo.dev/v1alpha1",
        "metadata": {
                "creationTimestamp": null
        },
        "s2iItems": [
                { ... }
         ]
        "devfileItems": [
                {
                        "Name": "",
                        "DisplayName": "Maven Java",
                        "Description": "Upstream Maven and OpenJDK 11",
                        "Link": "/devfiles/maven/devfile.yaml",
                        "Registry": {
                                "Name": "DefaultDevfileRegistry",
                                "URL": "https://raw.githubusercontent.com/elsony/devfile-registry/master"
                        }
                },
                {
                        "Name": "",
                        "DisplayName": "NodeJS Express Web Application",
                        "Description": "Stack with NodeJS 10",
                        "Link": "/devfiles/nodejs/devfile.yaml",
                        "Registry": {
                                "Name": "DefaultDevfileRegistry",
                                "URL": "https://raw.githubusercontent.com/elsony/devfile-registry/master"
                        }
                },
                {
                        "Name": "",
                        "DisplayName": "Open Liberty",
                        "Description": "Open Liberty microservice in Java",
                        "Link": "/devfiles/openLiberty/devfile.yaml",
                        "Registry": {
                                "Name": "DefaultDevfileRegistry",
                                "URL": "https://raw.githubusercontent.com/elsony/devfile-registry/master"
                        }
                },
                {
                        "Name": "",
                        "DisplayName": "Spring Boot®",
                        "Description": "Spring Boot® using Java",
                        "Link": "/devfiles/springBoot/devfile.yaml",
                        "Registry": {
                                "Name": "DefaultDevfileRegistry",
                                "URL": "https://raw.githubusercontent.com/elsony/devfile-registry/master"
                        }
                },
                {
                        "Name": "",
                        "DisplayName": "Quarkus Java",
                        "Description": "Upstream Quarkus with Java+GraalVM",
                        "Link": "/devfiles/quarkus/devfile.yaml",
                        "Registry": {
                                "Name": "DefaultDevfileRegistry",
                                "URL": "https://raw.githubusercontent.com/elsony/devfile-registry/master"
                        }
                }
        ]
}

## Expected behavior

Component names for devfile components should be present in plain text and json output 

## Any logs, error output, etc?


@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 24, 2020
@adisky
Copy link
Contributor

adisky commented Aug 25, 2020

@dgolovin you need to update devfile registry it should be https://github.com/odo-devfiles/registry

@dgolovin
Copy link
Contributor Author

@adisky we figured that out with @kadel. That is happening when I use some experimental versions before using latest one. It might be because the ~/.odo/preference.yaml is already there and has wrong registries in it. It should be probably fixed on odo side, by checking that the values in that file are correct for specific version of odo.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants