In 8.1 and earlier we used http://localhost:8088/web/status/sys.internaldb?39 to access the internal system db. I am finally migrating to 8.3 and updating our internal plugins and can see evidence of the old plugin objects in the migrated projects. I would like to properly migrate and remove dead objects from the database but need access to the internal database like previously. Is that feature still present? If so, what is the path or mechanism to access it?
No, it's not present, and the internal database is not used any longer in 8.3. We don't delete it after migrating the content out of it, but it's not used.
If by plugin you mean 3rd party module, your v8.3 modules are supposed to supply config DB migrators for the tables your module(s) own. The migrator is responsible for constructing new filesystem resources for the rows in your tables. The migration infrastructure keeps track of tables that have already been processed to avoid repeat migration.
The rest of your module is supposed to use the new resource infrastructure. (My understanding is that the migration infrastructure will not be present in 2027.2.)
Correct - most of this stuff is deprecated in 8.3 and will be removed in 2027.2.
What this means for users is that for the first time there will be a required version that you start on before upgrading. In this case, you'll have to be on 8.3 before upgrading to 2027.2.
Thank you. I understand and it is only a minor inconvenience for us to reenter configuration once so that is what we will do. So far it is mostly fine with this. The database access was useful on rare occasions and now that we have proper secrets management it fixes the other issues we had.