Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • V Vault
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 小 白蛋
  • Vault
  • Repository
Switch branch/tag
  • vault
  • api
  • client.go
Find file BlameHistoryPermalink
  • Sander van Harmelen's avatar
    Use a pooled HTTP client for the Vault CLI (#5734) · 76bc4216
    Sander van Harmelen authored Nov 09, 2018
    As the CLI client is initialized with a specific Vault address, is makes
    sense to use the pooled HTTP client here. This will prevent setting up
    new TCP sessions for each API call that the client needs to make.
    76bc4216

免费DevSecOps平台,让您的项目体验完整的DevSecOps流程,让项目更安全