You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ACR] Improvements to README, TSG and samples (Azure#25746)
### Packages impacted by this PR
- `@azure/container-registry`
### Issues associated with this PR
- Azure#25448
### Describe the problem that is addressed by this PR
- Add documentation about resumable upload 404 issue.
- Add select samples for blob operations to README to be consistent with
the other languages.
- Increment version in preparation for GA and republish samples.
Copy file name to clipboardExpand all lines: sdk/containerregistry/container-registry/CHANGELOG.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,20 @@
1
1
# Release History
2
2
3
-
## 1.1.0-beta.4 (Unreleased)
3
+
## 1.1.0 (2023-05-09)
4
4
5
5
### Features Added
6
+
- Added `ContainerRegistryContentClient` for uploading and downloading OCI blobs and manifests.
6
7
7
8
### Breaking Changes
8
9
9
-
### Bugs Fixed
10
-
11
-
### Other Changes
10
+
Since `1.1.0-beta.3`:
11
+
- The manifest property on GetManifestResult is now `Record<string, unknown>` instead of OciImageManifest. This property is now populated regardless of the media type of the manifest, instead of only being populated when the manifest was an OCI image manifest.
12
+
- Added an `isOciImageManifest` type guard to check if a manifest is an OCI image manifest, providing strong typing.
13
+
- Renamed properties on `OciImageManifest`, `OciDescriptor`, and `OciAnnotations` to match the specification exactly:
14
+
- Renamed `OciAnnotations.createdOn` to `created`.
15
+
- Renamed `OciDescriptor.sizeInBytes` to `size`.
16
+
- Renamed `OciImageManifest.configuration` to `config`.
17
+
- Removed `GetOciImageManifestResult` and the corresponding type guard, `isGetOciImageManifestResult`.
Copy file name to clipboardExpand all lines: sdk/containerregistry/container-registry/TROUBLESHOOTING.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,33 @@ RestError: {"errors":[{"code":"DENIED","message":"client with IP '<your IP addre
61
61
s/acr/firewall to grant access."}]}
62
62
```
63
63
64
+
## Service errors
65
+
66
+
When working with `ContainerRegistryContentClient` and `ContainerRegistryAsyncContentClient` you may get a `RestError` with
67
+
message containing additional information and [Docker error code](https://docs.docker.com/registry/spec/api/#errors-2).
68
+
69
+
### Getting BLOB_UPLOAD_INVALID
70
+
71
+
In rare cases, transient error (such as connection reset) can happen during blob upload which may lead a `RestError` being thrown with a message similar to
72
+
`{"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid"}]}`, resulting in a failed upload. In this case upload should to be restarted from the beginning.
73
+
74
+
The following code snippet shows how to access detailed error information:
0 commit comments