Skip to content

Commit

Permalink
Update Custom Executor variable names (#51)
Browse files Browse the repository at this point in the history
update variable names
  • Loading branch information
cjflan authored Oct 10, 2024
1 parent 68bd82a commit 529afed
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions GitLab/custom-executor.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,12 +59,12 @@ To do that:

The provided scripts expect the following environment variables to be set:

- `ORKA_TOKEN` - User authentication to connect to the Orka environment. Created by running `orka3 user get-token` or `orka3 serviceaccount token <service-account>`.
- `ORKA_ENDPOINT` - The Orka endpoint. Usually, it is `http://10.221.188.20`.
- `ORKA_CONFIG_NAME` - The name of the VM config to be deployed.
- `ORKA_VM_NAME_PREFIX` - The prefix of the generated VM name. Defaults to `gl-runner`.
- `ORKA_VM_USER` - User used to SSH to the VM.
- `ORKA_SSH_KEY_FILE` - The private SSH key contents to use when connecting to the VM. This key was created earlier during the Orka base image setup.
- `CUSTOM_ENV_ORKA_TOKEN` - User authentication to connect to the Orka environment. Created by running `orka3 user get-token` or `orka3 serviceaccount token <service-account>`.
- `CUSTOM_ENV_ORKA_ENDPOINT` - The Orka endpoint. Usually, it is `http://10.221.188.20`.
- `CUSTOM_ENV_ORKA_CONFIG_NAME` - The name of the VM config to be deployed.
- `CUSTOM_ENV_ORKA_VM_NAME_PREFIX` - The prefix of the generated VM name. Defaults to `gl-runner`.
- `CUSTOM_ENV_ORKA_VM_USER` - User used to SSH to the VM.
- `CUSTOM_ENV_ORKA_SSH_KEY_FILE` - The private SSH key contents to use when connecting to the VM. This key was created earlier during the Orka base image setup.

For more information about GitLab CI/CD environment variables, see [here][env-variables].

Expand Down

0 comments on commit 529afed

Please sign in to comment.