Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,059
    • Issues 1,059
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 53
    • Merge requests 53
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #4745
Closed
Open
Issue created Sep 30, 2019 by Balasankar 'Balu' C@balasankarcMaintainer

Provide a gitlab-ctl command for using Mattermost CLI with settings provided as environment variables

Since 11.0, we pass configuration to Mattermost as env variables. This means, users can't simply initiate mattermost binary with just the config file and expect the CLI to work fine, as it will be missing many settings. The workaround is being documented in !3644 (merged), but I think it would be easier for our users if we provide a gitlab-ctl mattermost-cli command which essentially does everything needed.

Assignee
Assign to
Time tracking