[mesheryctl] Removal of the onboard Sub-command from Mesheryctl Pattern Command

[singh1203]

Notes for Reviewers

This PR fixes #10886

Signed commits

• Yes, I signed my commits.

[github-actions]

[leecalcote]

@singh1203 will you list the various test scenarios that you've tried and their results?

[singh1203]

@singh1203 will you list the various test scenarios that you've tried and their results?

Currently haven't tested various scenarios, but will prioritize doing so ASAP and exploring different tests I can run.

[leecalcote]

Any scenarios and results to report, @singh1203?

[singh1203]

Any scenarios and results to report, @singh1203?

Certainly! Here is a list of the various test scenarios and their results for the mesheryctl pattern command:

mesheryctl pattern apply

• Applying with ID

  • Result: Failed
  • Issue: No pattern found with the given name or ID.
  • Error Message: "Fetching patterns... No Pattern found with the given name or ID."

• Applying with file path

  • Result: Partially successful
  • Issue: Pattern is created but not deployed.
  • Error Message: "Applying pattern Simple Kubernetes Pod. Response Status Code 500, possibly Server error."

• Index problem

  • Result: Failed
  • Issue: When providing an index, it shows "Already implemented with [pattern name]".

• Documentation issues

  • Issue: Missing proper documentation for the command syntax (e.g., mesheryctl pattern apply [patternID]).

mesheryctl pattern import

• Importing from local file

  • Result: Successful
  • Issue: None

• Importing from URL

  • Result: Failed
  • Issue: Unable to import using URL.
  • Opened issue [mesheryctl] Issue Converting Helm Chart to Kubernetes Manifest when Importing Design via URL #10960

mesheryctl pattern delete

• Deleting with patternID

  • Result: Successful
  • Issue: None

• Deleting with file path

  • Result: Failed
  • Issue: Response Status Code 500, possibly Server error.
  • Error Message: "Unable to create a response from request. Response Status Code 500, possibly Server error."

• Deleting with URL

  • Result: Failed
  • Issue: Unclear what is meant by URL in the command syntax (mesheryctl pattern delete {URL to patternfile}).

mesheryctl pattern offboard

• URL-based pattern deletion

  • Result: Not implemented
  • Issue: Lack of URL-based pattern deletion in the implementation.

• Redundancy with delete sub-command

  • Issue: There is no significant difference between the offboard and delete sub-commands, suggesting the offboard sub-command could be removed.

mesheryctl pattern view

• Viewing patterns
  • Result: Successful
  • Issue: Sometimes the response is too large to be fully viewed in the CLI.

mesheryctl pattern list

• Listing patterns
  • Result: Successful
  • Issue: None

[leecalcote]

@singh1203, good progress. Send word when the tests are passing.