Closed mudit-01 closed 1 year ago
Merging #5266 (e8a49f3) into main (16f2c15) will decrease coverage by
0.00%
. The diff coverage is0.00%
.
@@ Coverage Diff @@
## main #5266 +/- ##
==========================================
- Coverage 69.53% 69.52% -0.01%
==========================================
Files 197 197
Lines 16070 16070
==========================================
- Hits 11174 11173 -1
- Misses 4839 4840 +1
Partials 57 57
Flag | Coverage Δ | |
---|---|---|
unittests | 69.52% <0.00%> (-0.01%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files | Coverage Δ | |
---|---|---|
cmd/cli/version.go | 43.96% <0.00%> (ø) |
|
pkg/certificate/manager.go | 87.29% <0.00%> (-0.41%) |
:arrow_down: |
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
@keithmattix @shalier @jaellio @steeling go mock test is taking too much time PTAL thanks
Thanks, @jaellio for the comment, I tried with v1.2.1 but it did not show the new version
Even with OSM CLI v1.2.2 it do not show latest v1.2.3 available.
By moving logic it can output the desired new version
@jaellio PTAL, thanks
Thanks, @jaellio for the comment, I tried with v1.2.1 but it did not show the new version
Even with OSM CLI v1.2.2 it do not show latest v1.2.3 available.
By moving logic it can output the desired new version
Yes, you're correct! I missed the return statement on line 79.
LGTM
Thanks! @keithmattix for the review.
@jaellio @keithmattix we can merge this?
Thanks! @jaellio
Now OSM CLI version check will happen regardless of any K8s cluster
Signed-off-by: mudit singh mudit.singh@india.nec.com
Description: Earlier the OSM CLI version check only happened when there is K8s cluster present as below If no K8s cluster is present below is the output
Testing done: Yes Manual testing done below are the screenshots With K8s cluster
Without K8s cluster
Please answer the following questions with yes/no.