000-globals.yaml

#------------------------------------------------------------------------------
# Default settings for the charts that helmfile-deploy generates releases for:
#   - i.e. the bitsofinfo/appdeploy and bitsofinfo/appconduits charts
#
# These global defaults can be overriden in the following ways
# (all or a portion thereof)
#
# a) Re-declare in your own custom yaml files by adding additional *.yaml files
#    within the HELMFILE_DEPLOY_STATE_VALUES_DIR
#
# b) per helmfile "environment" YAML file. I.E. these could be declared in any
#    [HELMFILE_DEPLOY_ENVIRONMENTS_DIR]/[helmfile-environment]/[any-env-file.yaml]
#    - at the root level (i.e. just: chartConfigs)
#    - at the environments.[environmentName].chartConfigs level
#    - at the environments.[environmentName].contexts.[contextName] level
#    - at the environments.[environmentName].contexts.[contextName].services.[serviceName] level
#------------------------------------------------------------------------------

chartConfigs:

  appconduits:
    chart: bitsofinfo-appconduits/appconduits
    version: 1.1.4
    #
    # Further chart values customization:
    #
    # WTF is a "baseValuesRootDir"? Each helmfile environment can declare its own
    # customization of "chartConfigs" at various levels such as the below to
    # declare sets of default values to apply to each release using this chart.
    #
    # EXAMPLE:
    # For the below configuration the conduits.helmfile.yaml would expect
    # the following values.yaml files to exist:
    # (Assuming: )
    #
    # - ../custom-configs/myconfigs/chartvalues/appconduits/values/defaults/values.yaml
    # - ../custom-configs/myconfigs/chartvalues/appconduits/values/app1/stage/values.yaml
    # - ../custom-configs/myconfigs/chartvalues/appconduits/values/misc/stage/stage-qa/values.yaml
    # - ../custom-configs/myconfigs/chartvalues/appconduits/values/myappname/values.yaml
    #
    # Where in the below example you can reference any of the following 4 variables
    # in your "availableBaseValueSets" named set array items:
    #    - {{.appname}}
    #    - {{.classifier}} (if any)
    #    - {{.environmentName}} the current environment name for the release being created
    #    - {{.contextName}}" for the current context name for the release being created
    #
    # The values for the above TPL vars are from any of your YAML files @:
    #    $HELMFILE_DEPLOY_ENVIRONMENTS_DIR/environments/<helmfileEnvironmentName/*.yaml
    #
    #---------------
    #chartValues:
    #  baseValuesRootDir: "../custom-configs/myconfigs/chartvalues/appconduits"
    #
    #  # These are the actual value sets that will be includes out
    #  # of the "availableBaseValueSets" options below
    #  baseValueSets:
    #    - common
    #    - other
    #
    #  # These are the all available named base values sets, that can be referenced
    #  # by "name/key" above in "baseValueSets"
    #  availableBaseValueSets:
    #    common:
    #     - defaults
    #    other:
    #     - app1/{{.environmentName}}
    #     - misc/{{.environmentName}}/{{.contextName}}
    #     - {{.appname}}
    #
    #
    # You should specify the above in another custom values YAML in this same
    # directory OR via the helmfile command line directly such as:
    #
    # --state-values-set \
    #     chartConfigs.appconduits.chartValues.baseValuesRootDir=[relative path to baseValues root dir]
    #
    #
    ## You can also specify in-line custom "appconduits" chart values directly
    #values:
    #  conduitname: "newname"
    #  conduits:
    #    ...


  appdeploy:
    chart: bitsofinfo-appdeploy/appdeploy
    version: 1.4.7
    #
    # Further chart values customization:
    #
    # WTF is a "baseValuesRootDir"? Each helmfile environment can declare its own
    # customization of "chartConfigs" at various levels such as the below to
    # declare sets of default values to apply to each release using this chart.
    #
    # EXAMPLE:
    # For the below configuration the conduits.helmfile.yaml would expect
    # the following values.yaml files to exist:
    # (Assuming: )
    #
    # - ../custom-configs/myconfigs/chartvalues/appdeploy/values/defaults/values.yaml
    # - ../custom-configs/myconfigs/chartvalues/appdeploy/values/app1/stage/values.yaml
    # - ../custom-configs/myconfigs/chartvalues/appdeploy/values/misc/stage/stage-qa/values.yaml
    # - ../custom-configs/myconfigs/chartvalues/appdeploy/values/myappname/values.yaml
    #
    # Where in the below example you can reference any of the following 4 variables
    # in your "availableBaseValueSets" named set array items:
    #    - {{.appname}}
    #    - {{.classifier}} (if any)
    #    - {{.environmentName}} the current environment name for the release being created
    #    - {{.contextName}}" for the current context name for the release being created
    #
    # The values for the above TPL vars are from any of your YAML files @:
    #    $HELMFILE_DEPLOY_ENVIRONMENTS_DIR/environments/<helmfileEnvironmentName/*.yaml
    #
    #---------------
    #chartValues:
    #  baseValuesRootDir: "../custom-configs/myconfigs/chartvalues/appdeploy"
    #
    #  # These are the actual value sets that will be includes out
    #  # of the "availableBaseValueSets" options below
    #  baseValueSets:
    #    - common
    #    - other
    #
    #  # These are the all available named base values sets, that can be referenced
    #  # by "name/key" above in "baseValueSets"
    #  availableBaseValueSets:
    #    common:
    #     - defaults
    #    other:
    #     - app1/{{.environmentName}}
    #     - misc/{{.environmentName}}/{{.contextName}}
    #     - {{.appname}}
    #
    #
    # You should specify the above in another custom values YAML in this same
    # directory OR via the helmfile command line directly such as:
    #
    # --state-values-set \
    #     chartConfigs.appdeploy.chartValues.baseValuesRootDir=[relative path to baseValues root dir]
    #
    #
    ## You can also specify in-line custom "appdeploy" chart values directly
    #
    #values:
    #  app:
    #    classifier: "something"
    #  env:
    #    SOME_ENV_VAR:
    #      value: "whatever"


#------------------------------------------------------------------------------
# This section defines general configuration for the actual helmfile templates
# that generate the actual releases driven by each environment's yaml
#------------------------------------------------------------------------------
releaseConfigs:

  # Configs specific to appdeploy release generation
  # i.e. consumed in: @see deployments.helmfile.yaml
  deployments:
    # nothing yet

  # Configs specific to appconduits release generation
  # i.e. consumed in: @see conduits.helmfile.yaml
  conduits:

    # The "service" selector label "names" (i.e. keys) for standard
    # selector labels generated for all "appconduits" helmfile releases
    selectorlabelNames:
      appName: "app-name"
      appVersion: "app-version"
      appClassifier: "app-classifier"