Description

Related to #28384 and other issues we need to ensure that it's not necessary to modify buildtime options to run import / export.

This may also come into play with any kc.sh functionality we add around admin account access.

Users may also not realize that they need to specify all relevant runtime options that were supplied to their kc start.

This issue should likely cover #24191 as well.

Discussion

No response

Motivation

It is particularly confusing for users running the import / export from the same installation as the keycloak server because there is just a sinlge optimized jar location.

Details

For build time options we can:

• providing some way for import / export to use a different optimzed jar location
• stop allowing / using buildtime options for import / export

Related to this:

• we should ensure that the cache and all ports (the management port in particular) are disabled when running import / export

A final consideration would be to have a mode for import/export that can run against an existing server.