this is not planned at the moment. Also, the more detailed error messages are still quite internal. Prior to erratum 250, we only got the error code (e.g., 425 when the registration of an LDAP schema fails). Now we get this code plus one more detail depending on the error itself (for “425”, it is the exit code of an external function that actually tried to register the file). This is by no means a full log file. And most of the time, these errors relate to some functionality around the App installation process, not the actual installation. E.g., the Docker image could not be downloaded, the LDAP connection could not be established, UCS was unable to start a database for the Docker App.
Furthermore, all of this currently holds only for Docker Apps. Non-Docker Apps do not send any details, although we intend to change that in the future.
That being said, providing details about failed installations may be useful for App maintainers. Would you be able to “pack” any error in your installation routine into one small “error code”? Or extract the important lines of a long log file? Maybe we can think of a way to add this into the error handling.
But this would make at least one more errata update necessary.