Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 55k
    • Issues 55k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1.6k
    • Merge requests 1.6k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #251106
Closed
Open
Issue created Sep 18, 2020 by Grant Young@grantyoungDeveloper

Change Max Import Size limit setting to be disabled by default

Recently we (Quality) noticed today that a project import max size limit of 50mb is being enforced by default now on our omnibus based test environments. This appears to have added within the last week.

For Omnibus self managed installs typically we suggest for these limits to be disabled (see #223718 (comment 382174618) for a similar issue) and for users to opt in rather than get stung as each customer will likely always have unique needs and have to customise limits anyways. For example any customer now wanting to run GPT will absolutely hit this issue and make the process more complicated.

Looking around I can see Infra were stung with this on .com last week and tweaked it back accordingly but I can’t find the specific issue or MR for the change itself (although I found the MR to introduce the setting itself).

For the reasons about this should be removed before it makes it into a release.

Edited Sep 18, 2020 by Grant Young
Assignee
Assign to
Time tracking