Add diagnostic reports uploader, without Rails app context
What does this MR do and why?
Similar to !98781 (closed), but running without the Rails context.
How to set up and validate locally
Same as !98781 (closed), only 2 things are different:
- We no longer invoke
bundle exec rails runner
. So, to run it locally, just doGITLAB_DIAGNOSTIC_REPORTS_UPLOADER_SLEEP_S=3 GITLAB_DIAGNOSTIC_REPORTS_BUCKET=diag_reports GITLAB_DIAGNOSTIC_REPORTS_PROJECT=alipniagov-c14e6039 GITLAB_GCP_KEY_PATH=/Users/al/dev/gitlab-keys/gcs/gcloud.json GITLAB_DIAGNOSTIC_REPORTS_PATH=/Users/al/dev/tmp-diag-reports-uploads bundle exec ruby bin/diagnostic-reports-uploader
(with params replaced accordingly) instead. - To test in GKE, everything is the same as in the linked MR, except in gitlab-org/charts/gitlab!2791 (diffs) we no longer invoke the runner, run the files with
bundle exec ruby
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #372242 (closed)
Edited by Aleksei Lipniagov