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. Sep 01, 2024
  2. Sep 08, 2021
  3. Jul 23, 2020
  4. Oct 18, 2019
  5. Oct 08, 2019
  6. Aug 15, 2019
    • 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
  7. Aug 08, 2019
  8. Aug 02, 2019
    • Patrick Bajao's avatar
      Add Executable struct · 3b6f9f75
      Patrick Bajao authored
      This struct is responsible for determining the name and
      root dir of the executable.
      
      The `RootDir` property will be used to find the config.
      
      The `Name` property will be used to determine what `Command`
      and `CommandArgs` to be built.
      3b6f9f75
Loading