As we reevaluate how to best support and maintain Staging Ref in the future, we encourage development teams using this environment to highlight their use cases in the following issue: https://gitlab.com/gitlab-com/gl-infra/software-delivery/framework/software-delivery-framework-issue-tracker/-/issues/36.

Skip to content
Snippets Groups Projects
  1. Oct 03, 2019
  2. Oct 01, 2019
  3. Sep 30, 2019
  4. Sep 29, 2019
  5. Sep 26, 2019
  6. Sep 24, 2019
  7. Sep 20, 2019
  8. Sep 04, 2019
  9. Sep 02, 2019
  10. Sep 01, 2019
  11. Aug 30, 2019
  12. Aug 29, 2019
    • Patrick Bajao's avatar
      Repurpose bin/authorized_keys script · 4cee52bd
      Patrick Bajao authored
      It's been replaced by `gitlab-shell-authorized-keys-check` and
      it's also calling the `/authorized_keys` endpoint via Ruby.
      
      Since they have the same functionality as the new binary, better
      to call that instead to make it SSOT for authorized keys requests.
      4cee52bd
  13. Aug 20, 2019
  14. Aug 19, 2019
  15. Aug 15, 2019
    • Nick Thomas's avatar
      Merge branch '206-quick-fix' into 'master' · 81f58545
      Nick Thomas authored
      Replace symlinks with actual binaries
      
      Closes #206
      
      See merge request gitlab-org/gitlab-shell!324
      81f58545
    • Patrick Bajao's avatar
      Replace symlinks with actual binaries · 41f919eb
      Patrick Bajao authored
      We had `gitlab-shell-authorized-keys-check` and
      `gitlab-shell-authorized-principals-check` as symlinks to
      `gitlab-shell` before.
      
      We determine the `Command` and `CommandArgs` that we build based
      on the `Name` of the `Executable`. We also use that to know which
      fallback ruby executable should we fallback to. We use
      `os.Executable()` to do that.
      
      `os.Executable()` behaves differently depending on OS. It may
      return the symlink or the target's name. That can result to a
      buggy behavior.
      
      The fix is to create binaries for each instead of using a symlink.
      That way we don't need to rely on `os.Executable()` to get the name.
      We pass the `Name` of the executable instead.
      41f919eb
  16. Aug 14, 2019
  17. Aug 09, 2019
  18. Aug 08, 2019
  19. Aug 05, 2019
Loading