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

Compatibility mode on oras push #720

Closed
1 task
shizhMSFT opened this issue Dec 12, 2022 · 1 comment
Closed
1 task

Compatibility mode on oras push #720

shizhMSFT opened this issue Dec 12, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request ux User experience related
Milestone

Comments

@shizhMSFT
Copy link
Contributor

What is the version of your ORAS CLI

0.16.0

What would you like to be added?

Add a compatibility mode for oras push so that it can force pushing OCI image manifest instead of OCI artifact manifest.

Why is this needed for ORAS?

The state-of-the-art registries supports OCI artifact manifest. Since 0.16.0, oras push pushes OCI artifact manifest to those registries which support it. However, the new manifest type may not be supported at the consumer side (e.g. self-crafted scripts). It would be better if we can provide a compatibility mode for smoother migration from OCI image manifests to OCI artifact manifests.

The current workaround for enabling the combability mode is to specify a --config flag. Since OCI artifact manifest does not have a config, it will push an OCI image manifest instead. However, it is not user-friendly and is a bit hacky. We should provide a clearer way to do so.

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

  • Yes, I am willing to implement it.
@shizhMSFT
Copy link
Contributor Author

Resolved by #741

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ux User experience related
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants