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 formatted JSON output for oras copy #1226

Open
1 task
FeynmanZhou opened this issue Jan 3, 2024 · 0 comments
Open
1 task

Support formatted JSON output for oras copy #1226

FeynmanZhou opened this issue Jan 3, 2024 · 0 comments
Labels
enhancement New feature or request format output spec required Issues that require specifications
Milestone

Comments

@FeynmanZhou
Copy link
Member

FeynmanZhou commented Jan 3, 2024

What is the version of your ORAS CLI

ORAS v1.1.0

What would you like to be added?

When writing the feature spec ORAS formatted output, the --format flag is not considered in oras copy because its scenario is not common and clear enough.

We do see users want to find out all the referrers that did get copied and their digest and artifactType that got copied over in the output. But this feature request has not been justified as a common scenario in the community and can even be achieved by using formatted JSON output of oras discover.

This issue is created for gathering more potential use cases of using formatted JSON output with oras copy. If you have any requirements or scenarios related to this feature request, feel free to comment on this issue.

Why is this needed for ORAS?

N/A

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 Jan 3, 2024
@yizha1 yizha1 removed the triage New issues or PRs to be acknowledged by maintainers label Jan 9, 2024
@yizha1 yizha1 added this to the future milestone Jan 9, 2024
@FeynmanZhou FeynmanZhou modified the milestones: future, v1.3.0 Mar 4, 2024
@FeynmanZhou FeynmanZhou added the spec required Issues that require specifications label Mar 14, 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 format output spec required Issues that require specifications
Projects
None yet
Development

No branches or pull requests

2 participants