use pull always policy for secure operations

changed the description

@bbodenmiller For reference, I think you are referring to adding pull_policy to the runner config by default. Is that correct?

@michaelmcleroy yes setting pull_policy = "always" right above helper_image = ... would do it.

The always pull policy should be used if your runner is publicly available and configured as a shared runner in your GitLab instance

I think this makes sense to do given this statement in the Gitlab docs. The default runner deployed via BB is deployed this way as an instance wide shared runner.

@bbodenmiller this issue has been inactive for 30 days and is being labelled as stale. If this issue is still required please take action by removing the stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken this issue will be auto closed in 60 days.

Still awaiting fix. I do not have permissions to update labels.

added stale label

removed stale label

@bbodenmiller this issue has been inactive for 30 days and is being labelled as stale. If this issue is still required please take action by removing the stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as delete-me. If no action is taken this issue will be auto closed in 60 days.