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

odo init - welcoming messages #5494

Closed
kadel opened this issue Feb 24, 2022 · 0 comments · Fixed by #5514
Closed

odo init - welcoming messages #5494

kadel opened this issue Feb 24, 2022 · 0 comments · Fixed by #5514
Assignees
Labels
area/init Issues or PRs related to `odo init` kind/task Issue is actionable task

Comments

@kadel
Copy link
Member

kadel commented Feb 24, 2022

/kind task

I had issues with my connection and when I run odo init it took a few seconds before it showed any output.
It looks like it is trying to do Alizer analysis as a first thing.

There should be a message displayed first. So user is aware that odo is doing something

odo init can run in two modes. In an empty directory. Or with directory with existing code.

In empty directory the welcoming message should be something like:

The current directory is empty.
Odo will help with you starting a new project.

With directory with source code:

The current directory already contains source code.
Odo will try to autodetect language and project type to select best suited Devfile for your project.

links

one of the acceptance criteria in

@openshift-ci openshift-ci bot added the kind/task Issue is actionable task label Feb 24, 2022
@kadel kadel moved this to Todo in odo v3-alpha1 Feb 24, 2022
@kadel kadel added area/init Issues or PRs related to `odo init` v3 labels Feb 24, 2022
@kadel kadel moved this from Todo to In Progress in odo v3-alpha1 Mar 1, 2022
@serenamarie125 serenamarie125 modified the milestone: v3.0.0-alpha2 Mar 2, 2022
Repository owner moved this from In Progress to Done in odo v3-alpha1 Mar 7, 2022
rm3l added a commit to rm3l/odo that referenced this issue Mar 15, 2022
This relates to [1], because users might have
similar symptoms (few seconds before any output)
when running either `odo dev` or `odo deploy`
in a source code directory with no Devfile,
and those commands try to do an `Alyzer` analysis first.

[1] redhat-developer#5494
rm3l added a commit to rm3l/odo that referenced this issue Mar 15, 2022
This relates to [1], because users might have
similar symptoms (few seconds before any output)
when running either `odo dev` or `odo deploy`
in a source code directory with no Devfile,
and those commands try to do an Alizer analysis first.

[1] redhat-developer#5494
rm3l added a commit to rm3l/odo that referenced this issue Mar 16, 2022
This relates to [1], because users might have
similar symptoms (few seconds before any output)
when running either `odo dev` or `odo deploy`
in a source code directory with no Devfile,
and those commands try to do an Alizer analysis first.

[1] redhat-developer#5494
openshift-merge-robot pushed a commit that referenced this issue Mar 18, 2022
This relates to [1], because users might have
similar symptoms (few seconds before any output)
when running either `odo dev` or `odo deploy`
in a source code directory with no Devfile,
and those commands try to do an Alizer analysis first.

[1] #5494
cdrage pushed a commit to cdrage/odo that referenced this issue Aug 31, 2022
…t-developer#5556)

This relates to [1], because users might have
similar symptoms (few seconds before any output)
when running either `odo dev` or `odo deploy`
in a source code directory with no Devfile,
and those commands try to do an Alizer analysis first.

[1] redhat-developer#5494
@rm3l rm3l added the v3 label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/init Issues or PRs related to `odo init` kind/task Issue is actionable task
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants