-
Notifications
You must be signed in to change notification settings - Fork 243
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
Speedup odo registry --details #6678
Speedup odo registry --details #6678
Conversation
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
56f5912
to
5aaa62f
Compare
5aaa62f
to
987d6f6
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.
Changes lgtm, and the speed is visible. One small change is to remove reference to devfileData
from L132.
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.
/hold
A side-effet is that the stack content is not available anymore in the JSON output of the command. This removal will break the IDE plugins.
Indeed, I think we'll need to check with the IDE plugins or find a way not to break the output structure..
After a quick search into the source code, the VSCode plugin seems to rely on the .devfileData.devfile
field from the odo registry --details
output.
See:
Yes, right. These lines particularly are using the Also the devfileData.devfile.metadata.name used in many places, for example |
987d6f6
to
24b378e
Compare
17bbda1
to
ce11905
Compare
I've made changes according to what has been discussed during cabal. See #6678 (comment) for more details. |
ab0407e
to
dcd0629
Compare
/override windows-integration-test/Windows-test |
@feloy: Overrode contexts on behalf of feloy: windows-integration-test/Windows-test 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. |
5c90fdf
to
02a0236
Compare
02a0236
to
c347db3
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Sounds good to me to remove the hold on this PR, now that we are pretty confident in not breaking the IDE plugins, no? What do you think? |
Yes, the JSON output is not changed by this patch, it should not break the IDE plugins |
Thanks for confirming. /hold cancel |
/override OpenShift-Integration-tests/OpenShift-Integration-tests Flaky e2e test
|
@feloy: Overrode contexts on behalf of feloy: OpenShift-Integration-tests/OpenShift-Integration-tests 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. |
What type of PR is this:
/kind feature
What does this PR do / why we need it:
odo registry --details -o json
continues to make new calls to get Devfile content for all stacks of registries (to not break plugin compatibility). This command will be deprecated, as--details
flag was not intended to be used without--devfile
flag.odo registry --details --devfile "name" -o json
continues to make a new call to get the "name" Devfile content (to not break plugin compatibility).odo registry --details
do not make anymore new calls to get Devfile content for all stacks of registries. This command will be deprecated, as--details
flag was not intended to be used without--devfile
flag.odo registry --details --devfile "name"
do not make anymore a new call to get the "name" Devfile content.Which issue(s) this PR fixes:
Fixes #6401
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: