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

Fix: vela def vet can be used without Kubernetes #6063

Merged
merged 1 commit into from
Jun 1, 2023

Conversation

Somefive
Copy link
Collaborator

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:

  • Read and followed KubeVela's contribution process.
  • Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
  • Run make reviewable to ensure this PR is ready for review.
  • Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

@codecov
Copy link

codecov bot commented May 31, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.15 ⚠️

Comparison is base (e215b18) 66.21% compared to head (ffd749d) 66.06%.

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     
Flag Coverage Δ
core-unittests 54.96% <ø> (-0.06%) ⬇️
e2e-multicluster-test 30.67% <ø> (-0.13%) ⬇️
e2etests 33.03% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 12 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@Somefive Somefive marked this pull request as draft June 1, 2023 01:44
Signed-off-by: Somefive <yd219913@alibaba-inc.com>
@Somefive Somefive marked this pull request as ready for review June 1, 2023 02:21
@@ -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())
Copy link
Collaborator

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?

Copy link
Collaborator Author

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

@chivalryq chivalryq merged commit eb4b1a8 into kubevela:master Jun 1, 2023
20 of 21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants