Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,970
    • Issues 36,970
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,431
    • Merge requests 1,431
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #323290

Closed
Open
Created Mar 03, 2021 by Russell Dickenson@rdickensonMaintainer

Add documentation on how to use Secure's features at scale

Problem to solve

We are missing information that helps customers operating above the SME scale. Such companies are left to determine by themselves how to scale the various Secure configurations to hundreds or more projects. For example, the SAST offline documentation includes instructions on implementing a change per project. This is a very inefficient method of applying changes. Instead, the instructions should instruct the user to implement these changes at the instance level.

Proposal

  • Add documentation on how companies can implement Secure's features efficiently and effectively. Example:
    • Add documentation on how settings can be used at the instance and group level, to make settings deployment more efficient.

Who can address the issue

Other links/references

technical-writing#343

Edited Mar 03, 2021 by Russell Dickenson
Assignee
Assign to
13.12
Milestone
13.12
Assign milestone
Time tracking