Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cryptic error message when copying tar to repository #111

Open
joaopapereira opened this issue Mar 29, 2021 · 1 comment
Open

Cryptic error message when copying tar to repository #111

joaopapereira opened this issue Mar 29, 2021 · 1 comment
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request good first issue An issue that will be a good candidate for a new contributor Hacktoberfest Issues that are ready for Hacktoberfest participants. priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence but not planned. Contributions are welcome. snack This issue has been identified as lightweight and potentially quick to deliver.

Comments

@joaopapereira
Copy link
Member

Describe the problem/challenge you have
When copying a tar, or a bundle to a repository, when the destination provided in the command line contains a tag, or have no repository, or is malformed in some way the error message is not very helpful
ex:

imgpkg copy --tar some-bundle-v0.1.0.tar --to-repo localhost:5000
Error: Building import repository ref: repository can only contain the runes `abcdefghijklmnopqrstuvwxyz0123456789_-./`: localhost:5000

Describe the solution you'd like
imgpkg should be able to replace the message that is provided by the ggcr library with an easier understand message.
When a tag is present it should say: cannot specify a tag in the destination repository
When is malformed it should say destination repository is not valid. The format allowed is registry.io/some-image or registry.io:11111/some-image


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 bug fixed as soon as possible"
👎 "There are more important bugs to focus on right now"

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

@joaopapereira joaopapereira added enhancement This issue is a feature request carvel triage This issue has not yet been reviewed for validity labels Mar 29, 2021
@joaopapereira
Copy link
Member Author

Going to accept this story as a UX improvement.

@joaopapereira joaopapereira added carvel accepted This issue should be considered for future work and that the triage process has been completed and removed carvel triage This issue has not yet been reviewed for validity labels Apr 7, 2021
@iamhsk iamhsk added the good first issue An issue that will be a good candidate for a new contributor label Apr 19, 2021
@aaronshurley aaronshurley added priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence but not planned. Contributions are welcome. snack This issue has been identified as lightweight and potentially quick to deliver. labels Aug 26, 2021
@DennisDenuto DennisDenuto added the Hacktoberfest Issues that are ready for Hacktoberfest participants. label Oct 6, 2021
@aaronshurley aaronshurley moved this to To Triage in Carvel Jul 25, 2022
@github-project-automation github-project-automation bot moved this to To Triage in Carvel Feb 14, 2023
@joaopapereira joaopapereira moved this from To Triage to Unprioritized in Carvel Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request good first issue An issue that will be a good candidate for a new contributor Hacktoberfest Issues that are ready for Hacktoberfest participants. priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence but not planned. Contributions are welcome. snack This issue has been identified as lightweight and potentially quick to deliver.
Projects
Status: Unprioritized
Development

No branches or pull requests

4 participants