Google Cloud Blob Store
Only available in Sonatype Nexus Repository Pro. Interested in a free trial? Start here.
When creating a new Google Cloud Storage blob store in Sonatype Nexus Repository, you will configure the fields described in the sections below.
Give your blob store a unique name.
In Google Cloud, a project is a container containing related resources for a Google Cloud solution. In this case, you should enter the unique Google Cloud Project ID for the project that owns the bucket where blobs will be stored.
You can provide the projectId value from UI or let Nexus Repository automatically retrieve it from your configuration, properties file (nexus.gcloud.projectId), or credentials JSON file.
Provide a globally unique name for the Google Cloud bucket where blobs will be stored. As a best practice, follow Google Cloud Storage naming conventions.
Provide the path within your Cloud Storage bucket where blob data should be stored. For example, enter "blob-data/" as the path prefix to store data in a folder named "blob-data."
Enter the region where the Google Cloud bucket is hosted; this should be the same region in which Nexus Repository is running.
To access your Google Cloud Storage bucket, Nexus Repository needs to authenticate with Google Cloud. There are two options for authentication:
Use Google Application Default Credentials - This option uses the credentials already configured in your environment, simplifying setup and enhancing security. You can also directly provide a service account key file. See Google's documentation about application default credentials.
Use a separate credential JSON file - This option provides more granular control over authentication. You can use a dedicated service account with specific permissions for accessing your Google Cloud Storage bucket. Select this option to upload a service account key file (JSON) through the user interface. This service account must have permission to access your Google Cloud Storage bucket. See Google's documentation on creating and deleting service account keys.
This section allows you to enable a soft quota for the blob store, which will raise an alert when a blob store exceeds a constraint. See Adding a Soft Quota for more information.