Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedinexedi
  • gitlab-ce
  • Repository
  • gitlab-ce
  • config
  • gitlab.yml.example
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Use S3 Workhorse client with consolidated object store settings · 17f2052a
    Stan Hu authored Jun 27, 2020
    In GitLab 13.1.0, we added an S3 client to Workhorse
    (https://gitlab.com/gitlab-org/gitlab-workhorse/-/merge_requests/466).
    Previously this client would only be enabled if AWS instance profiles
    (use_iam_profile) were used. We extend this functionality if the
    consolidated object storage settings are enabled for AWS.
    
    This will fix ETag Mismatch errors with non-AWS S3 providers and pave
    the way for supporting encrypted S3 buckets with customer-provided keys.
    
    Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/220288
    17f2052a
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7