Skip to content
Snippets Groups Projects

Native Step Runner Integration for Docker Executor

Merged Axel von Bertoldi requested to merge avonbertoldi/47414/steps-integration-docker into main
2 unresolved threads
Compare and Show latest version
6 files
+ 194
10
Compare changes
  • Side-by-side
  • Inline
Files
6
@@ -83,6 +83,7 @@ The flags are defined in `./helpers/featureflags/flags.go` file.
| `FF_USE_LEGACY_S3_CACHE_ADAPTER` | `false` | **{dotted-circle}** No | | When enabled, the legacy S3 Cache adapter is used. When disabled (default), a newer S3 Cache adapter is used which uses Amazon's S3 SDK for authentication. This should resolve authentication problems in environments that the legacy adapter struggled with, such as custom STS endpoints. |
| `FF_GIT_URLS_WITHOUT_TOKENS` | `false` | **{dotted-circle}** No | | When enabled, GitLab Runner doesn't embed the job token anywhere during Git configuration or command execution. Instead, it sets up a Git credential helper that uses the environment variable to obtain the job token. This approach limits token storage and reduces the potential for leaks. |
| `FF_WAIT_FOR_POD_TO_BE_REACHABLE` | `false` | **{dotted-circle}** No | | When enabled, the runner waits for the Pod status to be 'Running', and for the Pod to be ready with its certificates attached. |
| `FF_USE_NATIVE_STEPS` | `false` | **{dotted-circle}** No | | When enabled and when a job is specified using the 'run' keyword, steps are executed using [Native Step Runner Integration](../executors/docker.md#native-step-runner-integration). This applies only to executors that support native steps integration like Docker, Docker Autoscaler, Docker for Windows. |
<!-- feature_flags_list_end -->
Loading