## Path           : System/Management
## Description    : Cloud Builder global settings
## Type           : string
## Default        : ""
#
# Cloud Builder compatible github packages/images source project
#
CB_PROJECT="https://github.com/OSInside/cloud-builder-packages.git"

## Type:        integer
## Default:     30
#
# Update interval for polling on new requests for
# the services cb-info, cb-scheduler and cb-fetch.
# The value specifies to wait N seconds before retry
# the poll on the message broker
#
CB_UPDATE=30

## Type:        integer
## Default:     10
#
# Cloud Builder build limit
# Allow up to CB_BUILD_LIMIT build processes at the same time
#
CB_BUILD_LIMIT=10

## Type:        integer
## Default:     5
#
# Cloud Builder package collector wait N seconds of
# inactivity on the info message broker service before
# working on the read results
#
CB_COLLECT_TIMEOUT=5

## Type:        integer
## Default:     30
#
# Cloud Builder package collector wait N seconds
# before asking for package/image updates again
#
CB_COLLECT_UPDATE_INTERVAL=30

## Type:        string
## Default:     ""
#
# Configure the response behavior of cb-info. By default
# a request to cb-info for a package/image for which the
# runner has no information will result in no answer from
# the service. If CB_INFO_RESPONSE_TYPE is set to
#
# --respond-always
#
# the behavior changes in a way that cb-info will
# send an answer for any received request, independently
# if there is data available or not.
#
CB_INFO_RESPONSE_TYPE=""

## Type:        string
## Default:     ""
#
# Path to the SSH private key used for connecting the
# runners such that non interactive access to the runners
# is possible. Sensitive information, please protect from
# third party access
#
CB_SSH_PKEY=""

## Type:        string
## Default:     ""
#
# Name of SSH user to use for accessing runners
#
CB_SSH_USER="cb-collect"

## Type:        integer
## Default:     0
#
# Cloud Builder runner count. Specify the number of runners
# that exists in the cluster. This information will be used
# in services which asks for information from the cb-info
# service. Each runner provides an info service. On request
# multiple info services could respond with information about
# a package/image. As the requester doesn't know how many
# answers completes the record, the default behavior is to
# wait for a configurable time of silence on the response
# queue before handing control back to the user and working
# on the results.
#
# This can lead to an unneeded amount of waiting time for
# the user. There is also always the risk that the wait time
# was not long enough to retrieve all answers from the
# cb-info services in the system.
#
# If the information about the number of runners in the
# cluster is provided, this value will be used to count the
# number of answers and if that number equals the number
# of runners it is clear that there can't be more answers
# which leads the reading code to get back to the user
# instead of staying blocked waiting for the timeout.
#
# If the number of runners in the cluster is specified here
# it is also required that all cb-info services are configured
# with:
#
# CB_INFO_RESPONSE_TYPE="--respond-always"
#
# The default value of 0 runners indicates there is no
# knowledge about the amount of runners in the system and that
# leads to the timeout based behavior as explained above
#
CB_RUNNERS=0
