-
Notifications
You must be signed in to change notification settings - Fork 858
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
Fix: vela def vet can be used without Kubernetes #6063
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #6063 +/- ##
==========================================
- Coverage 66.21% 66.06% -0.15%
==========================================
Files 193 193
Lines 25123 25127 +4
==========================================
- Hits 16635 16600 -35
- Misses 6878 6912 +34
- Partials 1610 1615 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Somefive <yd219913@alibaba-inc.com>
5779b59
to
ffd749d
Compare
@@ -772,7 +773,7 @@ func NewDefinitionRenderCommand(c common.Args) *cobra.Command { | |||
} | |||
config, err := c.GetConfig() | |||
if err != nil { | |||
return err | |||
klog.Infof("ignore kubernetes cluster, unable to get kubeconfig: %s", err.Error()) |
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.
which parts of feature in this command rely on this config?
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.
So it is due to the usage of legacy PackageDiscover. But it is actually not working now so the config is not required. We will remove it entirely in #6031
Description of your changes
vela def vet
should not need Kubernetes environment to run. This is useful because CUE community can therefore run CI without KinD or KubeBuilder in their docker container to verify if the version upgrade of CUE won't break the usage of KubeVela.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
Special notes for your reviewer