Hello Everyone!
This thread will be kept up to date with release notes for Cloud Content Delivery. It will also have an updated list of known issues.
Release Notes
[u][u]December 2, 2020____[/u][/u]
We’ve released the API v0.9.87.
Summary
- Changed service so that billing is no longer deactivated when the last bucket is deleted for a project. The project needs to be archived to deactivate billing
- Added new params to the release diff entries endpoint: GetReleaseDiffEntries. You can now diff based upon release numbers or release ids. The new query params are ‘fromreleasenum’ and ‘toreleasenum’
- Added filter to the diff entries endpoints GetDiffEntries,GetReleaseDiffEntries. You can now filter entries by using ‘include_states’ and specifying a list of change states. For example: ‘include_states=Add,Delete,Update’
[u][u][u][u]December 1, 2020____[/u][/u][/u][/u]
An overview support page is now available in the dashboard. This page gathers the following info and analytics:
Summary
- You can see your bandwidth consumption at the project level
- You can keep track of the total bandwidth used with details of the free bandwidth used and paid bandwidth used
**[u]November 24, 2020**[/u]
We’ve released the API v0.9.79.
Summary
- Added new endpoint for Org usage
- Added missing foreign keys
- Configured the client API garbage collector
- Change queries for bucket and release lists to do far fewer queries
- Reworked how diffs are generated to create less load on the management server
____[u]November 6, 2020____[/u]
We’ve released the API v0.9.73.
Summary
- Added created field to bucket model
- Reworked diff generation to prevent locking on uploads
- Updated SSL cert
- Reworked statistics gathering to improve performance
- Moved to stricter caching policy for the client API, to include HEAD requests and 404s
October 15, 2020
We’ve released the API v0.9.62.
Summary
- Documentation: fix “Try it out” button
- Documentation: added release notes
- Added ApiKeyAuth to all routes secured by it in docs.json
- Added /orgs GET route
- Re-worked file storage to prevent race conditions when uploading identical files (size + hash) with different filenames. The last file completely uploaded is the version that is served.
October 8, 2020
We’ve released the API v0.9.61, CLI v0.9.8, and some updates in the dashboard.
Summary
- This release adds support for editing the notes fields on releases after the release has been created (editing available via CLI and dashboard)
- This release adds a support page in the dashboard. You can now see the API service status in real-time, submit a support ticket, and access documentation for Cloud Content Delivery in the CCD section.
Dashboard
A support page is available in the dashboard. This page gathers the following information and links:
- The status of Management and Client APIs in real time
- Direct links to assistance: forum, documentation, and API reference
- Direct submission of a support ticket
- Main Cloud Content Delivery materials
API v0.9.61
- Added a PUT route to releases to update notes on a release after a release has been created.
CLI v0.9.8
-
Added ‘releases update [releaseid] --notes’ to CLI to update notes after a release has been created
-
Fixed error messages when a user does not have access to perform an operation to inform them they need to be a manager or owner of the project.
September 30, 2020
We’ve released the API v0.9.60 and CLI v0.9.7
Summary
-
This release adds support for resuming uploads and downloads through the management API. Technical details are provided below.
-
The “entries download” command in the CLI has been changed to write to file by default rather than STDOUT.
API v0.9.60
-
Added a PUT route to releases to update notes on a release after a release has been created.
-
You can no longer download partial content through the client API. To download content through the client API the size (Content-Size) and MD5 hash (Content-Hash) must match. The client API will return a 404 if they do not match. We still support downloading incomplete files through the management API. Files uploaded before this release will still be available through the client API.
-
If you upload the expected number of bytes (or more) for a file and the Content-Hash does not match the Upload-Offset will be reset to zero, and you will need to upload again. You can still download the file through the management API for troubleshooting purposes.
-
Support has been added for tus uploads (https://tus.io/). This includes a POST endpoint for the /content routes. This route is NOT required to be called. It’s simply for tus clients that break without it.
-
Added x-unity-hash to content status endpoints. This includes md5, crc32c, sha1, and sha256 hashes when available. MD5 should be available for all files. The rest will only be available for new uploads. They headers looks like this:
X-Unity-Hash: md5=4221d002ceb5d3c9e9137e495ceaa647
X-Unity-Hash: crc32c=163c5da7
X-Unity-Hash: sha1=804d716fc5844f1cc5516c8f0be7a480517fdea2
X-Unity-Hash: sha256=b6668cf8c46c7075e18215d922e7812ca082fa6cc34668d00a6c20aee4551fb6 -
You can now continue a partially uploaded file (or upload in partial segments). When continuing an upload you must start from the returned Upload-Offset or 0 to start over.
-
The value of x-unity-hash will reflect what has been uploaded with partial uploads.
-
Any files uploaded before this release will be assumed to be complete if their sizes match. No hash checks will be done.
-
Any new file uploads will need to have matching Content-Size and Content-Hash MD5 hashes to be added to a release.
CLI v0.9.7 (optional upgrade)
-
BREAKING: When using “entries download” the file will be downloaded to a local file with the same filename as the remote file. Previous behavior downloaded to STDOUT. You can continue to download to stdout using the output argument with a single dash:
–output - -
BREAKING: When using “entries download” if a file exists and you try to overwrite it the command will fail. You will need to use the --force flag to overwrite the existing file.
-
When using “entries download” you can resume partial downloads. Simply pass the --continue flag.