Check out our video below to learn more about all the latest updates in Cloud Content Delivery (CCD).
The latest CCD update now allows users to configure buckets’ write conditions so that only owners and managers can modify the content from certain buckets via the promotion process.
In CCD, you can build and configure content releases by packaging assets into buckets, which can then be categorized based on your specific needs. For example, developers can create different buckets for environments like “Development”, “Staging”, and “Production”. Following this, you can move assets from “Development” to “Staging” for testing, then promote the release to “Production” once it’s ready to go live.
What all this means is that this latest update helps to avoid errors when adding content to buckets, like uploading incorrect or unfinished assets to a production bucket.
Additionally, new bucket icons now indicate whether the bucket is either “Open to all” (an open box icon) or “Promotion only” (a closed box icon). If a bucket is tagged “Open to all”, anyone can modify content in this bucket, whereas the “Promotion only” tag only allows owners and managers to modify content through promotion from another bucket. No one else can upload content to, or delete content from, this type of bucket.
In an added step to improve access rights in CCD, we’ve implemented Private buckets. These are protected buckets that prevent unintended access and retrieval of content.
Private buckets protect read access to buckets with an access token, so that only those users with that token can retrieve content.
One application for the use of a Private bucket is creating a pre-release bucket of content that is only meant for developer integration and testing. Another may be an untested bucket that is meant for QA to review before being promoted to a “Staging” bucket.
Private buckets can also be used to segment content and allow access to specific audiences. For example, you can create one Private bucket for Android users and another for iOS users, each with their own unique security token.
Also, you now also have the option to edit buckets in a new Settings page in the CCD dashboard, as well as the ability to view, create, edit or delete bucket access tokens.
The newest Addressables package simplifies the integration between Addressables and CCD. With this latest update, once you’ve created a bucket in the CCD Dashboard, creating a new release, assigning a badge, and uploading content for that release can all be done via the Unity Editor.
To get started, make sure you’ve updated to the most recent Addressables Package. Then, you can create a new Build and Load path variable for your existing Addressables profile. With the new path pair created, navigate to the Bundle Location window and select Cloud Content Delivery.
Clicking “Create new bucket” will then link you directly to the appropriate CCD dashboard where you can upload content to the new bucket and select the relevant badge.
Once you’ve created your new path pair variable, you can also assign the Build and Load paths of various Addressables Asset Groups to it. Asset bundles will be automatically uploaded to the correct bucket and tagged as a new release when you hit the new “Build & Release” button in the Addressables Groups window.
We’ve updated the CCD onboarding guide to help you onboard team members quicker and scale up your use of the tool with the least amount of friction.
Once you’ve linked a new project to CCD, you can access the onboarding guide on the dashboard. The first step will be to choose the appropriate setting for your project (whether or not your project is using the Addressable Asset System).
Next, you’ll be prompted to create your first bucket. One of CCD’s main functionalities is to upload asset bundles to buckets, and then badge and distribute them to designated players. You can create custom buckets and badges based on your needs.
For example, a content release can be promoted from a “Development” bucket to a “Production” bucket in order to be deployed to players.
Depending on whether you’re using the Addressable Asset System or AssetBundles, you’ll follow the next steps in order to start uploading content to the buckets you’ve created. From there, you can start deploying content releases for your project.