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

Support customizing file name in oras pull #1159

Open
1 task
FeynmanZhou opened this issue Nov 1, 2023 · 3 comments
Open
1 task

Support customizing file name in oras pull #1159

FeynmanZhou opened this issue Nov 1, 2023 · 3 comments
Labels
enhancement New feature or request spec required Issues that require specifications ux User experience related
Milestone

Comments

@FeynmanZhou
Copy link
Member

What is the version of your ORAS CLI

v1.1.0

What would you like to be added?

Currently, oras pull saves the artifact with the name of the file that is stored in the annotations of the manifest. However, this makes it hard to find the file after pulling the file to local since users will need to go figure out what the annotation is and search for the file name, eventually find the file with the annotation as a reference. This is really cumbersome for users or for machines to find a pulled file.

In some cases, if the artifact that has multiple layers, we need to provide an option that allows to give file names to multiple pulled files. We will need to define the flags and experience to cover sing-layer and multi-layer scenarios.

Why is this needed for ORAS?

It would be much convenient if there is an option that points to a file (instead of a folder) and save the file with a given name, so users can easily find and use the pulled file for other operations later. This will be efficient and helpful in the automation or CI/CD scenario.

Are you willing to submit PRs to contribute to this feature?

  • Yes, I am willing to implement it.
@FeynmanZhou FeynmanZhou added enhancement New feature or request triage New issues or PRs to be acknowledged by maintainers labels Nov 1, 2023
@qweeah qweeah added this to the future milestone Nov 6, 2023
@qweeah
Copy link
Contributor

qweeah commented Nov 6, 2023

Putting it to future to avoid being marked as stale.

@qweeah
Copy link
Contributor

qweeah commented Nov 8, 2023

This looks similar to #346. +@ndeloof who helped raise the issue.

@FeynmanZhou
Copy link
Member Author

Maintainers suggested moving this issue to v1.3.0 milestone per discussion on Nov 7, 2023

@sajayantony sajayantony modified the milestones: future, v1.3.0 Nov 8, 2023
@yizha1 yizha1 removed the triage New issues or PRs to be acknowledged by maintainers label Nov 14, 2023
@FeynmanZhou FeynmanZhou added the ux User experience related label Mar 5, 2024
@FeynmanZhou FeynmanZhou added the spec required Issues that require specifications label Mar 14, 2024
@FeynmanZhou FeynmanZhou modified the milestones: v1.3.0, v1.4.0 Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request spec required Issues that require specifications ux User experience related
Projects
None yet
Development

No branches or pull requests

4 participants