lasdf1234 opened a new issue, #12218:
URL: https://github.com/apache/gravitino/issues/12218
### Describe the feature
Introduce a secret-provider SPI (`GravitinoSecretProvider`) so Gravitino can
store and resolve entity connection secrets through pluggable backends.
Initial scope:
- SPI lifecycle and CRUD-style secret operations (`initialize` / `type` /
`writeSecret` / `readSecret` / `deleteSecret` / `close`)
- process-local `InMemorySecretsProvider` for development and unit tests
- minimal supporting types (`SecretWriteContext`, `SecretUrn`,
`SecretConstants`)
Out of scope for the first PR: provider registry wiring,
REST/create-alter-drop
flows, and external secret references.
### Motivation
Entity connection properties (for example JDBC passwords) should not stay as
plaintext in metadata. A provider SPI is the OSS foundation for write-through
secrets, resolve/omit-on-read, and later KMS-backed or external backends.
### Describe the solution
Add `org.apache.gravitino.secret` types in `core`, with default no-op
`initialize`/`close` so simple providers stay constructor-only, and a Base64
in-memory provider marked non-production / non-encryption.
### Additional context
Follow-up work can add registry configuration, create-time write-through,
resolve/omit helpers, and REST exposure.
--
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]
