Environment Definition - csap-platform/csap-core GitHub Wiki

Related :     Application Editor     Application Model     Service Definition    

Concepts

CSAP environments enable applications to be "shaped" to a specific form. Consider the following common scenarios:

  • development may be a single host, with limited disk, cpu, and memory
  • production may be hundreds of hosts
  • performance may be a scale of production

CSAP environments can be configured leveraging the following core concepts:

  • Inheritance - environments may import settings from 1 or more other environments
  • Templates - any environment may be customized during installation using CSAP Auto Play
  • Configuration Maps - environments can use variables (template and environment) to customize behavior

Configuration Maps

The ability to define variables in configuration maps, and then refer to them in CSAP Service Templates enables quick refactoring and single locations to specify environment specific settings. All variables in the configuration map either be added to the "global" namespace, or selectively imported on a per service basis.

In order to be used in templates, variables must be named **$$**my-variable. ONLY those variables needing to be referenced in templates need to be named in this fashion; all others will simply be included in the OS environment variables as specified.

⚠️ **GitHub.com Fallback** ⚠️