lefebsy commented on PR #389:
URL: https://github.com/apache/polaris/pull/389#issuecomment-2699276840

   Hello,
   
   Last refactoring vending only STS.
   - Support of **profile** to manage credentials used by catalog to 
communicate with S3
   - Refactor the **duplicated functions** used by 'Aws' and also by 
'S3Compatible'. They have been moved to _StorageUtil_, here they should be 
imported and used by 'S3Compatible' or either by 'Aws' if this place is adopted.
   
   ```
   curl -X POST -H "Authorization: Bearer ${SPARK_BEARER_TOKEN}" \
        -H 'Accept: application/json' -H 'Content-Type: application/json' \
        http://${POLARIS_HOST}:8181/api/management/v1/catalogs -d \
         '{
             "name": "my-s3compatible-catalog-1",
             "id": 100,
             "type": "INTERNAL",
             "readOnly": false,
             "properties": {
               "default-base-location": "${S3_LOCATION}"
             },
             "storageConfigInfo": {
               "storageType": "S3_COMPATIBLE",
               "allowedLocations": ["${S3_LOCATION}/"],
               "s3.endpoint": "https://localhost:9000";
             }
           }'
   ```
   As is AWS SDK will use all default values and settings available in Polaris 
service, to build catalog communication to S3 endpoint
   
   
   Otherwise indications can be given 
   ```
             # optional - 'Indicate a AWS Profile name'
             "s3.profileName": "minio-catalog-1",
   ```
   or
   ```
             # optional - 'Indicate Env variable name'
             "s3.credentials.catalog.accessKeyEnvVar": 
"CATALOG_S3_KEY_ID_FOR_CATALOG_1",
             "s3.credentials.catalog.secretAccessKeyEnvVar": 
"CATALOG_S3_KEY_SECRET_FOR_CATALOG_1",
   ```
   and if helpful
   ```
             # optional
             "s3.region": "region-1",
             "s3.pathStyleAccess": true,
             "s3.roleArn": "arn:xxx:xxx:xxx:xxx:xxx"
   ```
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to