shared-config.yml

---
# If offline mode is enabled, bytes are fetched from an S3-compatible location, otherwise they are downloaded from bosh-io.
offline-mode:
   boshreleases: false # Enable or disable boshreleases offline mode, thus its download location. Default: false (disabled)
   stemcells: false # Enable or disable stemcells offline mode, thus its download location. Default: true (enabled)

lock-releases: false # Default: false. See https://bosh.io/docs/locking-compiled-releases/
# Shared pipelines configuration
shared:
  excluded_root_deployments:
    k8s: # exclude some root deployments from k8s shared pipelines management
      - a_root_deployment
      - another_root_deployment

default:
  reconciliation-loop:
     interval: 6h # Default 4m. You may override concourse k8s pipelines job frequency, ie interval between execution when nothing happen.
  #retry: # Configure how to handle retries in various context
    # task: 2 # Optional. You may override number of retry when running concourse tasks (except put, get and bosh deploy)
    # pull: 2 # Optional. You may override number of retry when getting data from external system like git, s3, etc...
    # push: 2 # Optional. You may override number of retry when sending data to external system like git, s3, etc...
    # bosh-push: 2 # Optional. You may override number of retry when sending data to bosh
  #bosh-options: # Optional. You may override bosh deploy default options for all deployments. To customize only a specific deployment, see 'deployment-dependencies.yml'
    # cleanup: true # Optional. An boolean that specifies if a bosh cleanup should be run after deployment. Defaults to true.
    # no_redact: false # Optional. Removes redacted from Bosh output. Defaults to false.
    # dry_run: false # Optional. Shows the deployment diff without running a bosh deploy. Defaults to false.
    # fix: false # Optional. Recreate an instance with an unresponsive agent instead of erroring. Defaults to false.
    # max_in_flight: # Optional. A number of max in flight option. Default: unset, use bosh max in flight
    # recreate: false # Optional. Recreate all VMs in deployment. Defaults to false.
    # skip_drain: # Optional. A collection of instance group names to skip running drain scripts for. Defaults to empty.
  stemcell:
    name: 56  # Default: bosh-openstack-kvm-ubuntu-bionic-go_agent
  concourse:
    # You can limit job execution per pipeline, static jobs are not affected by this restriction. Only jobs that are
    #  added or removed are limited. You can define the maximum number of jobs executed in parallel.
    parallel_execution_limit: 5 # Default: -1, ie unlimited
    # when parallel execution limit is active, you can choose the placement strategy used to group jobs.
    #   - SerialGroupRoundRobinNamingStrategy: each job is dispatched to a dedicated pool using round-robin strategy. We
    #           have a non-deterministic allocation, but good repartition.
    #   - SerialGroupMd5NamingStrategy: each job is dispatched to a dedicated pool using md5 hash and some computation.
    #           we have a deterministic allocation, but repartition cannot be guarantied. Recommended for on-demand services
    serial_group_naming_strategy: SerialGroupRoundRobinNamingStrategy #Default: SerialGroupRoundRobinNamingStrategy
  #git:
    # shallow-clone-depth: 1 # Default: 0, ie disabled

#<root-deployment-name>: # override per root-deployment
#  reconciliation-loop:
#     interval: 1h # Default 4m
#  retry:
#    task: 1 # Default: 2
#    pull: 3 # Default: 2
#    push: 4 # Default: 2
#    bosh-push: 5 # Default: 2
#  stemcell:
#    name: my-region-stemcell # Can be useful with multiple regions
#  git:
#    shallow-clone-depth: 1 # Default: 0, ie disabled
#  concourse:
#    parallel_execution_limit: 10 # Default: -1, ie unlimited
#    serial_group_naming_strategy: SerialGroupMd5NamingStrategy #Default: SerialGroupRoundRobinNamingStrategy
#  precompile:
#    excluded_deployments: [] # Default: [] # List of deployments to exclude from precompile. Since precompile does not use secrets repository to determine enabled deployments, it may be useful to exclude a deployment that is not enabled in secrets.
#    disabled_compiled_download_url_deployments: [] # Default: [] - List of deployments to exclude from bosh manifest precompile patching
#    disabled_compiled_download_url_deployments_prefix: [] # Default: [] - List of deployments prefix to exclude from bosh manifest precompile patching
#    disabled-cached-releases: [] # Default: [] - List of bosh releases to compile on local bosh director, even when compiled