mj006648 commented on issue #1325:
URL: https://github.com/apache/polaris/issues/1325#issuecomment-4448579574
Quick update after looking at the existing docs structure.
What's already there:
-
`getting-started/deploying-polaris/cloud-deploy/quickstart-deploy-{aws,azure,gcp}.md`
— quick-start path (added in #1435)
-
`configuration/configuring-polaris-for-production/configuring-gcs-cloud-storage-specific.md`
— short server-side page for GCS
What seems missing for the end-to-end sysadmin perspective:
- AWS S3 and Azure Blob equivalents of the GCS production config page
- Client-side wiring (Spark / Trino / PyIceberg) for each backend
- A clear single entry point that walks an admin from server config to
client connection to verification
Before I start, could you confirm which scope fits your intent:
Option 1 — minimal gap fill:
Add `configuring-aws-s3-cloud-storage-specific.md` and
`configuring-azure-blob-cloud-storage-specific.md` mirroring the existing GCS
page, server-side only. Client-side wiring and skill.md as separate follow-ups.
Option 2 — full E2E guide:
Per-backend pages covering server config, client connection, and
verification in one place. Existing GCS page gets expanded to match. skill.md
follows.
Option 1 lands faster; Option 2 is closer to the start-to-finish sysadmin
walkthrough you described. Which one do you prefer?
--
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]
