mj006648 opened a new pull request, #4451:
URL: https://github.com/apache/polaris/pull/4451

   ## Summary
   Adds production configuration pages for AWS S3 and Azure Blob storage 
backends, mirroring the existing GCS page. Implements Option 1 of #1325 as 
agreed with @flyrain. GCS page enhancement and skill.md are intentionally left 
for follow-up PRs.
   
   Two new pages under 
`site/content/in-dev/unreleased/configuration/configuring-polaris-for-production/`:
   - `configuring-aws-s3-cloud-storage-specific.md`
   - `configuring-azure-blob-cloud-storage-specific.md`
   
   Each covers server-side `storageConfigInfo` fields, client wiring for Spark 
/ Trino / PyIceberg, and a verification SQL snippet.
   
   ## Verified end-to-end while writing this
   - MinIO + Polaris + Spark / Trino / PyIceberg 0.11.1: CREATE / INSERT / 
SELECT round-trips. Findings folded into the page (the required 
`vended-credentials-enabled` and native-S3 properties for Trino, and the 
`header.X-Iceberg-Access-Delegation` REST header for PyIceberg).
   - Ceph RGW with STS disabled: produced `Failed to get subscoped credentials` 
STS 400 — informed the new "Backends without STS support" subsection.
   - ADLS Gen2 (HNS) with a service principal: happy-path round-trip.
   - ADLS Gen2 with the SP's `Storage Blob Data Contributor` removed: 
reproduced `AuthorizationPermissionMismatch` 403 — informed the Azure 
troubleshooting bullet.
   
   AWS IAM trust-policy / KMS specifics and HNS directory-ACL behavior are 
described conservatively based on docs and the corresponding Polaris classes 
rather than from a live test against those exact features.
   
   ## Test plan
   - [x] Hugo site build succeeds locally (186 pages, no errors)
   - [x] Both new pages appear in the production-config sidebar
   - [ ] CI Hugo build passes
   - [ ] Reviewers confirm the conservative bullets (AWS IAM/KMS, Azure HNS 
ACL) match operational reality


-- 
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