feat: update solo context connect to connect to single remote cluster

[Ivo-Yankov]

Description

This pull request changes the following:

• Adds a clusterContextMapping property to LocalConfig
• Adds new task methods related to the solo context command command.
• Changes the flow of the command. It can be summerized as follows:

 - Determines which context to use to connect to a remote cluster based on the provided flags: `namespace`, `context`, `cluster`. The user is prompted for additional input if required, unless the `--quiet` flag is used, in which case the default settings from `kubeConfig` are used.
 - Connects to the remote cluster and pulls the `remoteConfig`
 - The `LocalConfig` is updated with cluster data from the `remoteConfig`. If new clusters are added to the deployment in the local config, the `clusterContextMapping` is updated.

Related Issues

• Closes Implement solo context connect - connects to a deployment and pulls back the RemoteConfig for single cluster deployment #755
• Closes bug: solo context connect prompts for cluster after already supplied #951
• Closes add a flag to pass email address into solo context connect #950

[github-actions]

Unit Test Results - Linux

  1 files  ±0   58 suites  +1   3s ⏱️ ±0s
229 tests +9  229 ✅ +9  0 💤 ±0  0 ❌ ±0 
239 runs  +9  239 ✅ +9  0 💤 ±0  0 ❌ ±0 

Results for commit ff5c910. ± Comparison against base commit a4ef700.

This pull request removes 8 and adds 17 tests. Note that renamed tests count towards both.

should not set invalid context mappings ‑ LocalConfig should not set invalid context mappings
should prompt for all flags if none are provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for all flags if none are provided
should prompt for cluster if no value is provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for cluster if no value is provided
should prompt for context if no value is provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for context if no value is provided
should prompt for namespace if no value is provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for namespace if no value is provided
should update local configuration with provided values ‑ ContextCommandTasks unit tests updateLocalConfig should update local configuration with provided values
should use cluster from kubectl if no value is provided and quiet=true ‑ ContextCommandTasks unit tests updateLocalConfig should use cluster from kubectl if no value is provided and quiet=true
should use namespace from kubectl if no value is provided and quiet=true ‑ ContextCommandTasks unit tests updateLocalConfig should use namespace from kubectl if no value is provided and quiet=true

should not set invalid clusterContextMapping ‑ LocalConfig should not set invalid clusterContextMapping
should prompt for clusters and contexts if selected deployment is not found in local config ‑ ContextCommandTasks unit tests selectContext should prompt for clusters and contexts if selected deployment is not found in local config
should prompt for context if selected cluster is not found in local config mapping ‑ ContextCommandTasks unit tests selectContext should prompt for context if selected cluster is not found in local config mapping
should prompt for context if selected deployment is found in local config but the context is not ‑ ContextCommandTasks unit tests selectContext should prompt for context if selected deployment is found in local config but the context is not
should set clusterContextMapping ‑ LocalConfig should set clusterContextMapping
should throw a validation error if clusterContextMapping format is not correct ‑ LocalConfig should throw a validation error if clusterContextMapping format is not correct
should update clusterContextMapping with provided context ‑ ContextCommandTasks unit tests updateLocalConfig should update clusterContextMapping with provided context
should update currentDeployment with clusters from remoteConfig ‑ ContextCommandTasks unit tests updateLocalConfig should update currentDeployment with clusters from remoteConfig
should update multiple clusterContextMappings with default KubeConfig context if quiet=true ‑ ContextCommandTasks unit tests updateLocalConfig should update multiple clusterContextMappings with default KubeConfig context if quiet=true
should update multiple clusterContextMappings with prompted context no value was provided ‑ ContextCommandTasks unit tests updateLocalConfig should update multiple clusterContextMappings with prompted context no value was provided
…

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Results - Windows

  1 files  ±0   58 suites  +1   13s ⏱️ -1s
229 tests +9  229 ✅ +9  0 💤 ±0  0 ❌ ±0 
239 runs  +9  239 ✅ +9  0 💤 ±0  0 ❌ ±0 

Results for commit ff5c910. ± Comparison against base commit a4ef700.

This pull request removes 8 and adds 17 tests. Note that renamed tests count towards both.

should not set invalid context mappings ‑ LocalConfig should not set invalid context mappings
should prompt for all flags if none are provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for all flags if none are provided
should prompt for cluster if no value is provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for cluster if no value is provided
should prompt for context if no value is provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for context if no value is provided
should prompt for namespace if no value is provided ‑ ContextCommandTasks unit tests updateLocalConfig should prompt for namespace if no value is provided
should update local configuration with provided values ‑ ContextCommandTasks unit tests updateLocalConfig should update local configuration with provided values
should use cluster from kubectl if no value is provided and quiet=true ‑ ContextCommandTasks unit tests updateLocalConfig should use cluster from kubectl if no value is provided and quiet=true
should use namespace from kubectl if no value is provided and quiet=true ‑ ContextCommandTasks unit tests updateLocalConfig should use namespace from kubectl if no value is provided and quiet=true

should not set invalid clusterContextMapping ‑ LocalConfig should not set invalid clusterContextMapping
should prompt for clusters and contexts if selected deployment is not found in local config ‑ ContextCommandTasks unit tests selectContext should prompt for clusters and contexts if selected deployment is not found in local config
should prompt for context if selected cluster is not found in local config mapping ‑ ContextCommandTasks unit tests selectContext should prompt for context if selected cluster is not found in local config mapping
should prompt for context if selected deployment is found in local config but the context is not ‑ ContextCommandTasks unit tests selectContext should prompt for context if selected deployment is found in local config but the context is not
should set clusterContextMapping ‑ LocalConfig should set clusterContextMapping
should throw a validation error if clusterContextMapping format is not correct ‑ LocalConfig should throw a validation error if clusterContextMapping format is not correct
should update clusterContextMapping with provided context ‑ ContextCommandTasks unit tests updateLocalConfig should update clusterContextMapping with provided context
should update currentDeployment with clusters from remoteConfig ‑ ContextCommandTasks unit tests updateLocalConfig should update currentDeployment with clusters from remoteConfig
should update multiple clusterContextMappings with default KubeConfig context if quiet=true ‑ ContextCommandTasks unit tests updateLocalConfig should update multiple clusterContextMappings with default KubeConfig context if quiet=true
should update multiple clusterContextMappings with prompted context no value was provided ‑ ContextCommandTasks unit tests updateLocalConfig should update multiple clusterContextMappings with prompted context no value was provided
…

♻️ This comment has been updated with latest results.

[github-actions]

E2E Test Report

 16 files  ±0  121 suites  ±0   1h 21m 51s ⏱️ + 2m 46s
256 tests ±0  256 ✅ ±0  0 💤 ±0  0 ❌ ±0 
259 runs  ±0  259 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit ff5c910. ± Comparison against base commit a4ef700.

♻️ This comment has been updated with latest results.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ -0.08% (target: -1.00%)	✅ 77.71%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (a4ef700)	19197	16504	85.97%
Head commit (ff5c910)	19476 (+279)	16729 (+225)	85.90% (-0.08%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#993)	323	251	77.71%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[codecov]

Codecov Report

Attention: Patch coverage is 77.70898% with 72 lines in your changes missing coverage. Please review.

Project coverage is 84.90%. Comparing base (a4ef700) to head (ff5c910).
Report is 28 commits behind head on main.

Files with missing lines	Patch %	Lines
src/core/config/local_config.ts	31.70%	56 Missing ⚠️
src/commands/context/configs.ts	78.04%	9 Missing ⚠️
src/commands/context/handlers.ts	66.66%	4 Missing ⚠️
src/commands/context/tasks.ts	98.50%	2 Missing ⚠️
src/commands/flags.ts	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #993      +/-   ##
==========================================
- Coverage   84.99%   84.90%   -0.09%     
==========================================
  Files          71       72       +1     
  Lines       19225    19476     +251     
  Branches     1305     1650     +345     
==========================================
+ Hits        16341    16537     +196     
+ Misses       2858     2819      -39     
- Partials       26      120      +94     

Files with missing lines	Coverage Δ
src/commands/base.ts	95.39% <100.00%> (+0.17%)	⬆️
src/commands/context/flags.ts	100.00% <100.00%> (ø)
src/commands/context/index.ts	63.49% <100.00%> (ø)
src/core/error_messages.ts	100.00% <100.00%> (ø)
src/core/helpers.ts	88.85% <100.00%> (-0.22%)	⬇️
src/core/templates.ts	72.46% <ø> (-0.40%)	⬇️
src/core/validator_decorators.ts	98.71% <100.00%> (+0.80%)	⬆️
src/commands/flags.ts	78.51% <66.66%> (ø)
src/commands/context/tasks.ts	93.65% <98.50%> (+5.89%)	⬆️
src/commands/context/handlers.ts	65.57% <66.66%> (+2.11%)	⬆️
... and 2 more

... and 27 files with indirect coverage changes

[swirlds-automation]

🎉 This PR is included in version 0.32.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀