This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 26 Feb, 2020 1 commit
    • Yuan Gao's avatar
      Add support for Amazon Elastic Container Service · 47506a75
      Yuan Gao authored
      * Support new option: netns, enable file system to mount in given network namespace
      * Support new option: awscredsuri, enable sourcing iam authorization from aws credentials relative uri
      * List openssl and util-linux as package dependency for IAM/AP authorization and command nsenter to mount file system to given network namespace
  2. 30 Jan, 2020 1 commit
    • stvhu's avatar
      Improvements to auth and access point support · 153b3462
      stvhu authored
      * Ensure that certificate renewals always use the original credentials source
      * Include file system ID in all client TLS certificates
      * Updates to man page and README
  3. 13 Jan, 2020 1 commit
  4. 23 Jul, 2019 1 commit
  5. 27 Aug, 2018 2 commits
    • Pit Kleyersburg's avatar
      Incorporate PR review by maxbecke · 07423ed9
      Pit Kleyersburg authored
      This includes the following changes:
      * Reduce inline comments that were mostly redundant to the code it
      * Added another example to the man-page to make clear that TLS is
      supported for CNAMEs. For that matter, all other options will also work
      without change, given that internally the CNAME will only be resolved to
      an FS-ID before handing back over to the same logic that is already in
      * Small modifications to better adhere to the given codestyle.
      * Adjusted log messages as suggested.
    • Pit Kleyersburg's avatar
      Allow a CNAME DNS-name in addition to the EFS ID · e9af4aa4
      Pit Kleyersburg authored
      This change introduces additional logic which allows the user to specify
      either a fully-qualified EFS DNS name, or a custom DNS name that
      resolves to a fully-qualified EFS DNS name via a CNAME record.
      The EFS DNS name will then be compared to the EFS name we would have
      expected for the given EFS ID. If it doesn't match, we'll show the user
      a readable error message for this to aid in troubleshooting.
      Once the EFS DNS name has been verified, the rest of the logic is
      untouched. This means that this change only impacts the parameter logic
      at the very start and does not touch anything of the already tested,
      more critical logic.
      Important: the usage and internal logic to mount by EFS ID is unchanged,
      making this change fully backwards compatible.
      Fixes #9.
  6. 09 Jul, 2018 1 commit