lasdf1234 opened a new pull request, #11167:
URL: https://github.com/apache/gravitino/pull/11167

   ### What changes were proposed in this pull request?
   
   This PR wires built-in IdP storage into Gravitino runtime on top of `main`, 
including:
   
   - Core metadata services (`IdpUserMetaService`, `IdpGroupMetaService`) and 
JDBC backend integration
   - `IdpManagerFactory` / `IdpManager` and `GravitinoEnv` lifecycle wiring
   - `idp-basic` plugin providers and SPI registration
   
   Rebased onto latest `apache/gravitino` `main` (merged with `-X theirs` so 
upstream changes take precedence on conflicts).
   
   Part of #10960 / subtask #11044
   
   ### Why are the changes needed?
   
   The relational storage classes and plugin mappers landed on `main` via 
#11127 and #11140, but runtime wiring (env initialization, JDBC backend 
delegation, provider loading) still needs to land so the built-in IdP storage 
is usable.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   ```bash
   ./gradlew :core:compileJava :plugins:idp-basic:compileJava 
:plugins:idp-basic:compileTestJava -PskipITs
   
   ./gradlew :core:test :plugins:idp-basic:test -PskipITs 
-PskipDockerTests=true -PskipWeb=true \
     --tests org.apache.gravitino.TestGravitinoEnv \
     --tests org.apache.gravitino.TestIdpManagerFactory \
     --tests 
org.apache.gravitino.storage.relational.service.TestIdpGroupMetaService \
     --tests 
org.apache.gravitino.storage.relational.service.TestIdpUserMetaService \
     --tests 
org.apache.gravitino.storage.provider.TestIdpBasicGroupMetaProvider \
     --tests org.apache.gravitino.storage.provider.TestIdpBasicUserMetaProvider
   ```
   
   Made with [Cursor](https://cursor.com)


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