Skip to content

Enable artifact guidance for ORAS #1062

@sajayantony

Description

@sajayantony

What is the version of your ORAS CLI

v1.1.0-rc1

What would you like to be added?

Continuing the conversation here since its about an ORAS CLI experience discussion. oras-project/oras-www#248 (comment) @qweeah

@sajayantony To align oras's behavior with this subtree, do we need to ban --config if no file specified in below scenario?

I think we can warn since this is guidance and not a MUST in the specification.
The above example has a config file but no blob and that is not a scenario that cannot be executed but not recommended.

Also we probably need to consider how to enable the user to pass in the config mediaType and also artifact-type.

❯ oras push --config config.json:application/example.config+json  localhost:5000/oras-test:push1 --artifact-type application/example
Error: --artifact-type and --config cannot both be provided

Why is this needed for ORAS?

Updated support for v1.1

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

  • Yes, I am willing to implement it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestquestionFurther information is requested

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions