-
Notifications
You must be signed in to change notification settings - Fork 244
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 registry -o json #5739
odo registry -o json #5739
Conversation
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
3a8b342
to
6131ed8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM. I added few comments however ;)
docs/website/versioned_docs/version-3.0.0/command-reference/json-output.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another small improvement about the error message if a wrong registry is specified.
Wouldn't it be better, from the user perspective, to report that the registry was not found in the registry list, rather than saying no deployable components found
?
❯ odo registry --devfile java-maven --devfile-registry fake-registry -o json
{
"message": "no deployable components found"
}
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rm3l The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
/test v4.10-integration-e2e |
Flaky tests on non related tests /override ci/prow/v4.10-integration-e2e |
@feloy: Overrode contexts on behalf of feloy: ci/prow/v4.10-integration-e2e In response to this:
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. |
* Doc odo registry * JSON output * Move structure for JSON output to api package * Doc for json output * Add integration tests * Review * Do not rely on devfile version for tests as it is too unstable
What type of PR is this:
/kind feature
What does this PR do / why we need it:
odo registry
odo registry -o json
api
packageWhich issue(s) this PR fixes:
Fixes #5644
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: