From c7a07e3326bf31858deb9caa20e3cf2810958f1c Mon Sep 17 00:00:00 2001 From: Colin Dean Date: Wed, 16 Jul 2025 11:31:17 -0400 Subject: [PATCH] Fixes VELA_ADDR example to include https This is the observed behavior on my company's internal Vela server. --- docs/reference/environment/variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/environment/variables.md b/docs/reference/environment/variables.md index d56dd28..9579a31 100644 --- a/docs/reference/environment/variables.md +++ b/docs/reference/environment/variables.md @@ -108,7 +108,7 @@ The following table includes variables only available when the step `id_request` | Key | Value | Explanation | | ---------------------- |---------------------------------------------------|---------------------------------------------------------------------| | `VELA` | `true` | environment is Vela | -| `VELA_ADDR` | `vela.example.com` | fully qualified domain name of the Vela server | +| `VELA_ADDR` | `https://vela.example.com` | fully qualified domain name of the Vela server | | `VELA_CHANNEL` | `vela` | queue channel the build was published to | | `VELA_DATABASE` | `postgres` | database Vela is connected to | | `VELA_HOST` | `vela-worker-1` | fully qualified domain name of the worker the build was executed on |