`kubectl get package` or `kctrl package available get` results in a non user friendly error when the package is not available

[praveenrewar]

What steps did you take: Run

kubectl get package foo.1.0.0

OR

kctrl package available get -p foo/1.0.0

where the package foo doesn't exist

What happened: Errored out with the message in both the scenarios:

internalpackages.internal.packaging.carvel.dev "cpnmubhh5oo2sc0" not found

What did you expect: The error message should have been something like

internalpackages.internal.packaging.carvel.dev "foo.1.0.0" not found

to make it more user friendly.

Anything else you would like to add:

Environment:

• kapp Controller version - v0.30.2
• Kubernetes version - v1.22.3

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

[github-actions[bot]]

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

[github-actions[bot]]

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.

[github-actions[bot]]

This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.