feat: allow select context for kubecm add and merge command

[cr7258]

Description

Add the --select-context parameter allowing the user to choose which context should be added when running the kubecm add and kubecm merge commands.

Test

Prepare two kubeconfig.

./kubecm list --config kubeconfig1
+------------+-------------+-------------+----------+-------------------------+--------------+
|   CURRENT  |     NAME    |   CLUSTER   |   USER   |          SERVER         |   Namespace  |
+============+=============+=============+==========+=========================+==============+
|      *     |   context1  |   cluster1  |   user1  |   https://example1.com  |    default   |
+------------+-------------+-------------+----------+-------------------------+--------------+

./kubecm list --config kubeconfig2
+------------+-------------+-------------+----------+-------------------------+--------------+
|   CURRENT  |     NAME    |   CLUSTER   |   USER   |          SERVER         |   Namespace  |
+============+=============+=============+==========+=========================+==============+
|      *     |   context2  |   cluster2  |   user2  |   https://example2.com  |    default   |
+------------+-------------+-------------+----------+-------------------------+--------------+
|            |   context3  |   cluster3  |   user3  |   https://example3.com  |    default   |
+------------+-------------+-------------+----------+-------------------------+--------------+
|            |   context4  |   cluster4  |   user4  |   https://example4.com  |    default   |
+------------+-------------+-------------+----------+-------------------------+--------------+

Run the kubecm add command with the --select-context parameter. The user needs to confirm each context to be imported. If the --select-context parameter is omitted, confirmation is not required.

./kubecm add --config kubeconfig1 -f kubeconfig2 --select-context

Run the kubecm merge command with the --select-context parameter.

./kubecm merge --config output  kubeconfig1 kubeconfig2 --select-context

If there is no context to add or merge, the program ends directly instead of asking Does it overwrite File xxx ?.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (changes only affecting documentation)

Checklist

• I have tested my changes locally and ensured they are functioning properly. Please run the make build and make test commands.
• I have added/updated unit or e2e tests to cover my changes.
• I have updated the relevant documentation. If you change commands or arguments, run make doc-gen to generate new documentation.

[the-label-bot]

The Label Bot has predicted the following:

Category	Value	Confidence	Applied Label
Kind	feature	0.701	✔️
Kind	M	0.962	✔️

[codecov]

Codecov Report

Attention: Patch coverage is 10.00000% with 27 lines in your changes are missing coverage. Please review.

Project coverage is 19.40%. Comparing base (c940d7b) to head (bd57195).

Files	Patch %	Lines
cmd/add.go	21.42%	9 Missing and 2 partials ⚠️
cmd/cloud_add.go	0.00%	10 Missing ⚠️
cmd/merge.go	0.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #952      +/-   ##
==========================================
- Coverage   19.54%   19.40%   -0.15%     
==========================================
  Files          21       21              
  Lines        2062     2077      +15     
==========================================
  Hits          403      403              
- Misses       1617     1630      +13     
- Partials       42       44       +2     

Flag	Coverage Δ
unittests	19.40% <10.00%> (-0.15%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sunny0826]

Thank you for your valuable contribution to this project! Your work is greatly appreciated.

[sunny0826]

It might be better to use String for this flag.

[sunny0826]

Perhaps GetString is used here and followed by the relevant checks: exists, does not exist, is empty, etc.
This would allow for better automated testing in e2e test.

selectContext, _ := ac.command.Flags().GetString("select-context")

[cr7258]

I want to choose contexts interactively, so I use bool type.

kubecm add -f kubeconfig1 --select-context

For my understanding, you want this:

kubecm add -f kubeconfig1 --select-context context1

It seems like we couldn't implement different types for the same flag (bool and string) in Cobra. So I think your idea should be implemented by a different flag.

[sunny0826]

Indeed, a new flag should be created here.

[sunny0826]

@cr7258 But this new flag is a new feature, which is not part of this PR, would you like to create a new PR to contribute this this feature? I will merge this PR first.

[cr7258]

@sunny0826 I will contribute this feature in a new PR.

[sunny0826]

extremely grateful !

[sunny0826]

LGTM
Thank you for your valuable contribution to this project! Your work is greatly appreciated. 🎆

[sunny0826]

@all-contributors please add @cr7258 for doc