Billy Zha

@sbdtu5498 Any update on this?

@shizhMSFT Do we also need `--registry-token-stdin`?

@sbdtu5498 So we need to add another flag to enable read identity token from stdin like: ```bash echo $TOKEN | oras login $REGISTRY --identity-token-stdin ```

Thanks @plooploops for this feature request. Can you elaborate on the scenarios of programmatically checking artifact status for oras `attach`, `discover` and `pull` repectively? Below are some minimal information needed...

@plooploops Thanks for the clarification. Here are some comments: 1) `artifactUrl`: I suggest to name it to `reference` since both OCI image and OCI artifact could have this field. And...

> Please use reference since thats has a well know definition in OCI. Good point. Updated inline. > I’m curious why do we need to digest and artifactDigest? We don't...

@plooploops This version looks good to me. One small thing to add: `reference` should contain scheme, e.g. `http[s]://.azurecr.io/my/repo@sha256:someHash`

> @qweeah are you open to removing the http(s) part for the reference field? @plooploops Sounds good if it helps automation. ``` oras attach myreg.azurecr.io/my/repo:tag \ --artifact-type "example/foo" logo.jpg:image/jpg \...

BTW I am using `github.com/containerd/console v1.0.3`

Had a discussion offline with @kkarmakarMS. To push an image from a local OCI image layout tarball to a registry, `oras cp` should be used instead of `oras push`.