Usage Ping control in gitlab.rb
Description
EE customers need the ability to turn off the usage ping at install time, know that it is turned off, and know that it can't be enabled from the web interface. Currently this is only configurable from within the web interface. As a matter of policy, some customers can not allow this to be turned on. It needs to be able to be configured at install time, not via the web interface afterward. This is extremely important for at least one key EEP customer.
Proposal
- Add support from the gitlab.rb file for turning off the usage ping in EE.
- The use (or not) of this switch needs to affect the web interface so that when the usage ping functionality is turned off in the gitlab.rb file it can not be re-enabled from within the web interface.
- The web interface should indicate that the usage ping is disabled
- Whether usage ping is turned off or not should be logged in the audit log when the setting is changed or the server is restarted.
Links / references
Documentation blurb
Some organizations wish to keep their usage of GitLab private as a matter of policy. To disable the GitLab usage ping, that sends a small amount of data back to GitLab, set the <variable_name> in the gitlab.rb file to . Then reconfigure GitLab via gitlab-ctl reconfigure
and restart it with gitlab-ctl restart
.
/cc: @victorwu