Configuration

Every Vender component exposes a set of typed inputs. Inputs let you customize behavior without forking the component — essential for meeting strict, environment-specific requirements.

Passing inputs

Inputs are declared under the component reference:

include:
  - component: $CI_SERVER_FQDN/arrcade/components/sonarqube@2.1.0
    inputs:
      sonar-host-url: https://sonar.internal
      fail-on-quality-gate: true
      coverage-threshold: 80

Input types

Components validate inputs at pipeline creation time. The supported types are:

• string — free-form text
• number — integer or float
• boolean — true or false
• array — a list of strings

If an input fails validation, the pipeline fails fast with a clear message rather than at runtime.

Overriding the base image

For locked-down environments you can point a component at your own mirrored UBI image:

include:
  - component: $CI_SERVER_FQDN/arrcade/components/python3@1.4.0
    inputs:
      base-image: registry.internal/ubi9/python-311:1.0

Environment variables

Components also read a small set of environment variables for cross-cutting configuration: