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

   …edential vending
   
     GCS buckets with HNS enabled require explicit folder creation and
     storage.folderAdmin permissions for managed folder operations. Without
     this, Iceberg table creation and Spark ingestion fail on HNS buckets.
   
     Changes:
     - Add hierarchicalNamespace boolean field to GcpStorageConfigInfo (OpenAPI 
spec)
     - Add @Nullable Boolean isHierarchicalNamespace() to 
GcpStorageConfigurationInfo
     - Generate storage.folderAdmin access boundary rule scoped to 
managedFolders/{path} for write locations when HNS is enabled
     - Plumb HNS flag through CatalogEntity model<->entity conversion
     - Add backward-compatible 3-param overload defaulting HNS to false
   
     Tests:
     - HNS enabled single bucket (read + write + folder rules)
     - HNS with multiple buckets and partial writes
     - HNS without writes (no folder rules)
     - HNS with separate metadata and data buckets
     - HNS same bucket with separate metadata/data paths
     - Non-HNS vs HNS rule count comparison
     - Config serialization round-trip
     - CatalogEntity round-trip with HNS flag
   
   <!--
   📝 Describe what changes you're proposing, especially breaking or user-facing 
changes. 
   📖 See https://github.com/apache/polaris/blob/main/CONTRIBUTING.md for more.
   -->
   
   ## Checklist
   - [ ] 🛡️ Don't disclose security issues! (contact [email protected])
   - [ ] 🔗 Clearly explained why the changes are needed, or linked related 
issues: Fixes #
   - [ ] 🧪 Added/updated tests with good coverage, or manually tested (and 
explained how)
   - [ ] 💡 Added comments for complex logic
   - [ ] 🧾 Updated `CHANGELOG.md` (if needed)
   - [ ] 📚 Updated documentation in `site/content/in-dev/unreleased` (if needed)
   


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