After updating the file, a restart of Artifactory will kick-in these changes, and it will switch to use the Google native client.
Note! If you used any of the dedicated JetS3t properties in the google-stoarge provider, these will not be honored by the new Google native client.
However, check if the parameter is exposed in the documentation, and if so, set it in the “google-storage-v2” provider section.
For example:
Using dedicated JetS3t properties:
<provider id="google-storage" type="google-storage">
<endpoint>commondatastorage.googleapis.com</endpoint>
<bucketName>BUCKET_NAME</bucketName>
<property name="httpclient.max-connections" value="300"/>
<identity>XXXXXX</identity>
<credential>XXXXXX</credential>
</provider>
Moving to google-storage-v2:
<provider id="google-storage-v2" type="google-storage-v2">
<endpoint>commondatastorage.googleapis.com</endpoint>
<bucketName>BUCKET_NAME</bucketName>
<maxConnections>300</maxConnections>
</provider>
In the above case, useInstanceCredentials is not defined.Therefore, the default value will be assigned, false, and the below flow of the authentication resolution order follows:
‘useInstanceCredentials’ == false && save creds file under the default path [arti_home_full_path]/etc/gcp.credentials.json.