Add help flag to gitlab-ctl restart
Problem to solve
As a system administrator, I want to use --help in gitlab-ctl restart command, so I can see the list of services to restart.
Intended users
User experience goal
The user should be able to see a list of services that can be restarted.
Proposal
Further details
The system administrator will see a list of services that can be restarted
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Gitlab core
Is this a cross-stage feature?
Links / references
Activity
added devopssystems groupdistribution typefeature labels
added customer label
added sectioncore platform label
mentioned in issue #243480 (closed)
mentioned in issue #246472 (closed)
mentioned in issue #249074 (closed)
mentioned in issue #254175 (closed)
mentioned in issue #257800 (closed)
mentioned in issue #262006 (closed)
It sounds like there are two issues to address here, one is a bug and the other is a feature request.
- Running `gitlab-ctl restart --<_any text_> should validate the text and exit with an error if it isn't a valid option, rather than giving a success code and/or restarting GitLab services.
- A feature request to add a
--helpoption togitlab-ctl restartto list the services that can be restarted individually.
We have #241133 to address the bug. I'm editing the description of this issue to only be about the feature request to add
--helpEdited by Larissa Lane
mentioned in issue gitlab-org/quality/triage-reports#503 (closed)
mentioned in issue gitlab-org/quality/triage-reports#561 (closed)
mentioned in issue gitlab-org/quality/triage-reports#637 (closed)
mentioned in issue gitlab-org/quality/triage-reports#702 (closed)
mentioned in issue gitlab-org/quality/triage-reports#735 (closed)
mentioned in issue gitlab-org/quality/triage-reports#823 (closed)
mentioned in issue gitlab-org/quality/triage-reports#864 (closed)
mentioned in issue gitlab-org/quality/triage-reports#935 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1013 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1094 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1200 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1251 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1362 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1400 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1526 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1561 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1674 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1776 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1862 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1972 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2052 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2135 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2198 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2302 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2399 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2468 (closed)
mentioned in issue gitlab-org/quality/triage-reports#2565 (closed)
moved to omnibus-gitlab#7398
