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

Provide an odo alizer -o json command #5642

Closed
1 task done
Tracked by #5554 ...
feloy opened this issue Apr 8, 2022 · 4 comments
Closed
1 task done
Tracked by #5554 ...

Provide an odo alizer -o json command #5642

feloy opened this issue Apr 8, 2022 · 4 comments
Assignees
Labels
area/json-output Issues or PRs related to JSON output (machine readable output)

Comments

@feloy
Copy link
Contributor

feloy commented Apr 8, 2022

odo should provide an alizer command with -o json flag, that will return the result of the alizer tool on the current directory.

$ odo alizer -o json
{
  "devfile": "go",
  "devfileRegistry": "StagingRegistry"
}

The caller will use the exit status of the command to get the error status. 0=> OK and (not 0) => Error

In case of error, the json output will be present in the stderr with the content:

{
  message: "..."
}

TODO:

@feloy feloy self-assigned this Apr 8, 2022
@feloy feloy mentioned this issue Apr 8, 2022
3 tasks
@feloy feloy moved this to For Review in odo v3-beta1 Apr 8, 2022
@feloy feloy moved this from For Review to Done in odo v3-beta1 Apr 13, 2022
@kadel
Copy link
Member

kadel commented Apr 13, 2022

As we discussed with people working on IDE plugins, this command should return all matches together with the score

@feloy feloy added the area/json-output Issues or PRs related to JSON output (machine readable output) label Apr 14, 2022
@kadel kadel mentioned this issue May 5, 2022
20 tasks
@kadel
Copy link
Member

kadel commented May 5, 2022

/status blocked
We need alizer to support returning multiple results sorted by confidence

@rm3l
Copy link
Member

rm3l commented May 6, 2022

BTW, I remember one comment from the past sprint demo was that alizer as a command did not seem obvious or self-descriptive. I think they suggested using something like odo identify or odo analyze. Shouldn't we rename this command as part of this issue? @kadel @feloy

@kadel
Copy link
Member

kadel commented May 10, 2022

Shouldn't we rename this command as part of this issue? @kadel @feloy

+1 for odo analyze

@kadel kadel moved this from Done to Todo in odo v3-beta1 May 16, 2022
@kadel kadel added the status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) label May 18, 2022
@kadel kadel closed this as completed Jun 8, 2022
Repository owner moved this from Todo to Done in odo v3-beta1 Jun 8, 2022
@rm3l rm3l added v3 and removed status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) labels Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/json-output Issues or PRs related to JSON output (machine readable output)
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants