Environment

To deploy a fully functional environment, the Ekara engine must first build an internal model of the environment. The model describes every aspect of the environment, including cloud provider(s) to use, machine node(s) to create or software stack(s) to deploy.

Components

The environment model is built from one or more component(s):

  • A component lives in a source repository which is fetched dynamically when necessary,
  • If a component contains an ekara.yaml file, it will be parsed and contribute to the environment model.

Read on about the component model for details.

Descriptor

The Ekara descriptor is a YAML file. By default it is named ekara.yaml and placed at the root level of a source repository:

<root>
    |-- ekara.yaml

Read on about the descriptor syntax for details.

Templating

Ekara uses the Go html/template library for its template engine:

  • Ekara descriptors are always templated,
  • Arbitrary files in components can also be templated if needed.

Read on about templating for details.