set `--why-run` option for the gitlab-ctl reconfigure chef solo run
When we are testing credential changes on gitlab.com it would be helpful if gitlab-ctl reconfigure
had an option to use the --why-run
option for chef-client so we can see changes before they are actually made.
How about if we set something like WHY_RUN or CHEF_CLIENT_EXTRA_OPTS in the environment for https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-ctl-commands/lib/gitlab_ctl/util.rb#L90 ?
Edited by John Jarvis