SQL Server

Manage Bucket Storage Class

See more Google Cloud Storage Examples

Demonstrates how to manage a bucket's default storage class.

See Cloud Storage Classes for information about storage classes.

SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    -- This example requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    -- This example uses a previously obtained access token having permission for the 
    -- scope "https://www.googleapis.com/auth/cloud-platform"

    -- In this example, Get Google Cloud Storage OAuth2 Access Token, 
    -- the service account access token was saved to a text file.  This example fetches the access token from the file..
    DECLARE @sbToken int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbToken OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    EXEC sp_OAMethod @sbToken, 'LoadFile', @success OUT, 'qa_data/tokens/googleCloudStorageAccessToken.txt', 'utf-8'

    -- ---- Step 1
    -- Create the JSON body of the PUT request that will be sent.

    -- {
    --   "storageClass": "[STORAGE_CLASS]"
    -- }
    -- 

    DECLARE @json int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @json OUT

    -- Be careful if using the "regional" storage class.  See the note below about the 400 error response.
    EXEC sp_OAMethod @json, 'UpdateString', @success OUT, 'storageClass', 'nearline'

    -- ---- Step 2
    -- Send a PUT equivalent to this curl command

    -- curl -X PUT --data-binary @[JSON_FILE_NAME].json \
    --     -H "Authorization: Bearer [OAUTH2_TOKEN]" \
    --     -H "Content-Type: application/json" \
    --     "https://www.googleapis.com/storage/v1/b/[BUCKET_NAME]?fields=storageClass"

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT

    EXEC sp_OAMethod @sbToken, 'GetAsString', @sTmp0 OUT
    EXEC sp_OASetProperty @http, 'AuthToken', @sTmp0

    EXEC sp_OAMethod @http, 'SetUrlVar', @success OUT, 'bucket_name', 'chilkat-ocean'
    DECLARE @url nvarchar(4000)
    SELECT @url = 'https://www.googleapis.com/storage/v1/b/{$bucket_name}?fields=storageClass'
    DECLARE @resp int
    EXEC @hr = sp_OACreate 'Chilkat.HttpResponse', @resp OUT

    EXEC sp_OAMethod @http, 'HttpJson', @success OUT, 'PUT', @url, @json, 'application/json', @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @sbToken
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END

    DECLARE @responseCode int
    EXEC sp_OAGetProperty @resp, 'StatusCode', @responseCode OUT
    IF @responseCode = 401
      BEGIN
        EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
        PRINT @sTmp0

        PRINT 'If invalid credentials, then it is likely the access token expired.'

        PRINT 'Your app should automatically fetch a new access token and re-try.'
        EXEC @hr = sp_OADestroy @sbToken
        EXEC @hr = sp_OADestroy @json
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END

    -- On my first try at running this code, I received the following error response:
    -- Response code: 400
    -- Response body
    -- {
    --  "error": {
    --   "errors": [
    --    {
    --     "domain": "global",
    --     "reason": "invalid",
    --     "message": "The combination of locationConstraint and storageClass you provided is not supported for your project"
    --    }
    --   ],
    --   "code": 400,
    --   "message": "The combination of locationConstraint and storageClass you provided is not supported for your project"
    --  }
    -- }
    -- 

    -- This was because my storage location was a Multi-regional location, and I tried to assign the "regional" storage class,
    -- which is not allowed. 


    PRINT 'Response code: ' + @responseCode

    PRINT 'Response body'
    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    PRINT @sTmp0

    -- A response code = 200 indicates success, and the response body contains the JSON
    -- 
    -- Response code: 200
    -- Response body
    -- {
    --  "storageClass": "NEARLINE"
    -- }
    -- 

    EXEC @hr = sp_OADestroy @sbToken
    EXEC @hr = sp_OADestroy @json
    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @resp


END
GO