youngkermit8-coder opened a new pull request, #2371:
URL: https://github.com/apache/rocketmq-dashboard/pull/2371

   ## What changed
   
   - add an idempotent `upgrade-studio-auth.sql` migration for existing MySQL 
volumes
   - keep the migrated user and session table definitions aligned with the 
canonical `schema.sql`
   - document the upgrade command before enabling login protection
   - add a regression test that runs the table creation twice on a pre-auth 
schema and verifies legacy data remains intact
   
   ## Why
   
   MySQL only runs `docker-entrypoint-initdb.d` when a volume is first 
initialized. Volumes created before persistent authentication was added 
therefore never receive `rmq_studio_user` or `rmq_studio_session`, so the first 
database-backed login fails before configured bootstrap users can be persisted.
   
   The new migration only creates missing tables. It does not modify existing 
users, sessions, or unrelated data.
   
   ## Validation
   
   - `mvn -Dtest=StudioAuthMigrationTest test` (1 test, 0 failures)
   - `mvn test` (1355 tests, 0 failures)
   - Checkstyle: 0 violations
   
   Fixes #2350
   


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