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
When using the private container registry setup in Lagoon, if you define a password in the lagoon API at the project level, but you have environment level variables defined. The check used will prioritise the environment level variable first, but if there is one not defined, it will set it to an empty value.
When using the private container registry setup in Lagoon, if you define a password in the lagoon API at the project level, but you have environment level variables defined. The check used will prioritise the environment level variable first, but if there is one not defined, it will set it to an empty value.
https://github.com/amazeeio/lagoon/blob/f2fe153eab7da3c932f8b66b5c7136115a8c1bdc/images/oc-build-deploy-dind/build-deploy-docker-compose.sh#L263-L268
The logic needs to be updated to check if the value is not empty before setting it.
The text was updated successfully, but these errors were encountered: