lasdf1234 opened a new issue, #13203:
URL: https://github.com/apache/gravitino/issues/13203

   ### What would you like to be improved?
   
   Several official Gravitino cloud-storage and credential-vending property 
keys are defined in constants/docs but missing from `PropertiesMetadata`. As a 
result, the server treats them as undeclared user properties. This causes two 
problems:
   
   1. **Current masking path** (`isHiddenProperty`): undeclared keys are never 
masked via metadata, relying only on secret URNs.
   2. **Upcoming fuzzy masking** (PR #12983): undeclared keys whose names match 
patterns like `credential`, `token`, or `access` may be incorrectly masked in 
`properties()` responses — e.g. `credential-providers`, 
`azure-storage-account-name`, `s3-token-expire-in-secs`.
   
   The Web UI reads catalog properties only from `properties()`, so 
misclassified keys break the edit experience.
   
   ### How should we improve?
   
   **A. Expand shared cloud metadata modules**
   - Add non-secret S3/OSS/Azure credential-config keys to 
`S3PropertiesMetadata`, `OSSPropertiesMetadata`, and `AzurePropertiesMetadata`.
   - Add `COSPropertiesMetadata` for Tencent COS credential-config keys.
   - Add `*-token-expire-in-secs` entries to 
`CredentialConfig.CREDENTIAL_PROPERTY_ENTRIES`.
   
   **B. Merge credential metadata into catalog modules**
   - Merge `CredentialConfig.CREDENTIAL_PROPERTY_ENTRIES` into Iceberg, Hive, 
and Paimon catalog properties metadata (Fileset already had this).
   - Merge missing Azure/GCS shared metadata into Paimon.
   
   **Fuzzy rule (follow-up with #12983)**
   - Apply name-based fuzzy masking only when `!metadata.containsProperty(key)`.
   
   Catalog-specific operational keys (Iceberg jdbc-driver, scan-plan-cache, 
etc.) are out of scope — they do not match fuzzy patterns and are not needed 
for frontend masking.


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