The order of the configuration in kaltura-config-all.sh

User kaltura is created in MySQL when you run kaltura-db-config.sh, but before that, when you run kaltura-es-config.sh, it tries to access MySQL with user kaltura and throws up an error log. .
Wouldn’t it be correct to modify kaltura-es-config.sh to run after kaltura-db-config.sh?

The OS is CentOS7.
I ran kaltura-config-all.sh in October.