<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary `gitlab/gitlab-ee:13.12.1-ee.0` is ignoring the configuration for `gitlab_rails['initial_shared_runners_registration_token'] ` ### Steps to reproduce **This works as expected:** ``` docker run --detach --rm \ --env GITLAB_OMNIBUS_CONFIG="gitlab_rails['initial_shared_runners_registration_token'] = 'runner-reg-token'; " \ --publish 8080:80 \ --name gitlab_13_11 \ gitlab/gitlab-ee:13.11.3-ee.0 ```  **This does not work as expected** ``` docker run --detach --rm \ --env GITLAB_OMNIBUS_CONFIG="gitlab_rails['initial_shared_runners_registration_token'] = 'runner-reg-token'; " \ --publish 8090:80 \ --name gitlab_13_12 \ gitlab/gitlab-ee:13.12.1-ee.0 ```  ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? The token is generated randomly, ignoring the configuration. <!-- Describe what actually happens. --> ### What is the expected *correct* behavior? The token is generated as per the configuration <!-- Describe what you should see instead. --> ### Relevant logs and/or screenshots See _Steps to reproduce_ <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> <!-- ### Output of checks --> <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> <!-- #### Results of GitLab environment info --> <!-- Input any relevant GitLab environment information if needed. --> <!-- <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> --> <!-- #### Results of GitLab application Check --> <!-- Input any relevant GitLab application check information if needed. --> <!-- <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> --> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->