Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • V Velero
  • 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
  • 小 白蛋
  • Velero
  • Repository
Switch branch/tag
  • velero
  • docs
  • support-matrix.md
Find file BlameHistoryPermalink
  • Bastian Hofmann's avatar
    Allow to use AWS Signature v1 for creating signed AWS urls · e13806e0
    Bastian Hofmann authored Oct 25, 2018
    Some aws implementations, for example the quobyte object storage, do not
    support the v4 signing algorithm, but only v1.
    This makes it possible to configure the signatureVersion.
    
    The algorithm implementation was ported from https://github.com/oNestLab/botocore/blob/d6c1be296e8cfe0706cb0c8bbcad9c095d0f4d09/botocore/auth.py#L860-L862
    which is used by the aws CLI client.
    
    This fixes https://github.com/heptio/ark/issues/811
    
    .
    Signed-off-by: default avatarBastian Hofmann <bashofmann@gmail.com>
    e13806e0

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