Skip to content

Add support for custom HTTP headers in GitLab CI #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lukeheath merged 4 commits into from
Jun 20, 2026
Merged

Add support for custom HTTP headers in GitLab CI #124

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
eee80bd
Add support for custom HTTP headers in GitLab CI
avltree9798 Jun 16, 2026
55844ae
Add support for custom HTTP headers in GitHub Actions
avltree9798 Jun 17, 2026
c5d71f4
Merge branch 'main' into gitlab-ci-custom-headers
lukeheath Jun 20, 2026
621a5ca
Apply suggestion from @lukeheath
lukeheath Jun 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 23 additions & 2 deletions .gitlab-ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@ fleet-gitops:
image: node:22
variables:
FLEET_DRY_RUN_ONLY: true
# Optional. Extra HTTP headers to send on every request to Fleet. They are applied to
# both the version check (curl) and all fleetctl commands (config set / gitops).
#
# Format: a comma-separated list of "Header:Value" pairs. Header values cannot contain
# commas. Leave empty to send no extra headers.
#
# Set the real value as a (masked) CI/CD variable in Settings > CI/CD > Variables, which
# overrides this default. Example for a Cloudflare Access service token:
# FLEET_CUSTOM_HEADERS: "CF-Access-Client-Id:<client-id>,CF-Access-Client-Secret:<client-secret>"
FLEET_CUSTOM_HEADERS: ""
Comment on lines +5 to +14
rules:
- if: $CI_PIPELINE_SOURCE == 'merge_request_event'
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
Expand All @@ -14,14 +24,25 @@ fleet-gitops:
- apt-get -qq update
- apt-get install -y 'jq=1.6-2.1*'
script:
# Parse FLEET_CUSTOM_HEADERS into argument arrays for curl and fleetctl.
- |
CURL_HEADER_ARGS=()
FLEETCTL_HEADER_ARGS=()
if [[ -n "$FLEET_CUSTOM_HEADERS" ]]; then
IFS=',' read -ra _CUSTOM_HEADERS <<< "$FLEET_CUSTOM_HEADERS"
for _header in "${_CUSTOM_HEADERS[@]}"; do
CURL_HEADER_ARGS+=(--header "$_header")
FLEETCTL_HEADER_ARGS+=(--custom-header "$_header")
done
fi
Comment on lines +31 to +37
- >
FLEET_VERSION="$(curl "$FLEET_URL/api/v1/fleet/version" --header "Authorization: Bearer $FLEET_API_TOKEN" --fail --silent | jq --raw-output '.version')"
FLEET_VERSION="$(curl "$FLEET_URL/api/v1/fleet/version" --header "Authorization: Bearer $FLEET_API_TOKEN" "${CURL_HEADER_ARGS[@]}" --fail --silent | jq --raw-output '.version')"
- >
if [[ -n "$FLEET_VERSION" ]] ; then
npm install -g "fleetctl@$FLEET_VERSION" || npm install -g fleetctl
else
echo "Failed to get Fleet version from $FLEET_URL, installing latest version of fleetctl"
npm install -g fleetctl
fi
- fleetctl config set --address $FLEET_URL --token $FLEET_API_TOKEN
- fleetctl config set --address $FLEET_URL --token $FLEET_API_TOKEN "${FLEETCTL_HEADER_ARGS[@]}"
Comment thread
avltree9798 marked this conversation as resolved.
- ./gitops.sh
Loading