You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Currently, all distributions are picking up the default admin credentials changes successfully in both 3.0.0 and 2.12.0. However there is still a lingering issue - if either a weak or no initial admin password is set, the install scripts from the build repo side keep executing, ending up failing at a later point (when the certs are not found). This is a bad user experience. Instead, we should gracefully fail install execution as soon as we detect weak/no initial admin password. This will be more clear as to the reason why the installation script failed.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently, all distributions are picking up the default admin credentials changes successfully in both 3.0.0 and 2.12.0. However there is still a lingering issue - if either a weak or no initial admin password is set, the install scripts from the build repo side keep executing, ending up failing at a later point (when the certs are not found). This is a bad user experience. Instead, we should gracefully fail install execution as soon as we detect weak/no initial admin password. This will be more clear as to the reason why the installation script failed.
The text was updated successfully, but these errors were encountered: