odo v3-alpha1

[kadel]

• Once even a single flag is provided it runs in non-interactive mode. All required information needs to be provided via flags
• If the command is executed without flags it can enter interactive mode
• every command should have -o flag to specify output format, and every command should support -o json

CLI structure for v3.0.0-alpha1

• odo login
  • as it is in v2
• odo logout
  • as it is in v2
• odo init
  • odo init #5297
  • odo init - bootstrap new project in empty directory #5470
  • odo init - add ability to create component with existing codebase #5408
• odo dev
  • odo dev #5299
• odo deploy
  • odo deploy #5298
• odo preference
  • integrating odo registry into odo preference #5402
• odo build
  • image
    • as it is in v2
• odo list
  • odo list #5405
• odo delete
  • component
    • odo delete component #5409
• odo version
  • as it is in v2
• odo utils
  • as it is in v2

opened as PR #5341 for easier collaboration and review

[dharmit]

odo component every command from “odo component *” already exists as a root command.

What should we replace the word component with in the commands odo catalog list components and odo catalog describe component?

[kadel]

What should we replace the word component with in the commands odo catalog list components and odo catalog describe component?

Not sure yet, but it might actually stay as component there

[valaparthvi]

@kadel Do you want to do the honors of closing this epic, or will that be done after v3-alpha1 is released?

[kadel]

it is done, we can close it
/close

[openshift-ci]

@kadel: Closing this issue.

In response to this:

it is done, we can close it
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.