lunar-config.yml
Lunar Configuration
lunar-config.ymlType: YAML file
Form:
version: 0 hub: host: <hub-host> grpc_port: <grpc-port> http_port: <http-port> insecure: <insecure-flag> catalogers: - <cataloger-object> - <cataloger-object> - ... domains: <domain-name>: <domain-object> <domain-name>: <domain-object> ... components: <component-name>: <component-object> <component-name>: <component-object> ... collectors: - <collector-object> - <collector-object> - ... initiatives: - <initiative-object> - <initiative-object> - ... policies: - <policy-object> - <policy-object> - ...
The file lunar-config.yml file is used to configure the behavior of Lunar. It is recommended that you create a new code repository for all Lunar configuration and place this file in the root of it.
At a high-level, the file contains information about how the Lunar primitives are configured, ranging from how information is collected from the SDLC via collectors, to how components are organized into domains, and how the health of components is evaluated via policies.
version
versionlunar-config.yml -> versionType:
numericRequired
The version field is used to specify the version of the configuration file. The current version is 0.
hub
hublunar-config.yml -> hubType:
objectRequired
The hub object contains configuration for the Lunar Hub server.
host
hostlunar-config.yml -> hub.hostType:
stringRequired
The host field is used to specify the host of the Lunar Hub server.
grpc_port
grpc_portlunar-config.yml -> hub.grpc_portType:
integerRequired
The grpc_port field is used to specify the port of the Lunar Hub server for GRPC connections.
http_port
http_portlunar-config.yml -> hub.http_portType:
integerRequired
The http_port field is used to specify the port of the Lunar Hub server for HTTP connections.
insecure
insecurelunar-config.yml -> hub.insecureType:
booleanOptional
Default:
false
The insecure field is used to specify whether to use insecure HTTP connections to the Lunar Hub server.
catalogers
catalogerslunar-config.yml -> catalogersType:
arrayOptional
Catalogers are used to synchronize software catalog information (such as domains, and components) with external systems.
For information on how to configure catalogers, see catalogers.
domains
domainslunar-config.yml -> domainsType:
objectOptional
Domains are used to group related components together. Domains are hierarchical and can contain other domains.
For information on how to configure domains, see domains.
components
componentslunar-config.yml -> componentsType:
objectOptional
Components are the units of code that Lunar monitors. A component can represent either a code repository, or a subdirectory in the case of a monorepo.
Components are associated with domains and can have tags. Through the tagging system, components are associated with collectors, and policies.
For information on how to configure components, see components.
collectors
collectorslunar-config.yml -> collectorsType:
arrayRequired
Collectors are used to collect live information from various sources to associate with individual components.
For information on how to configure collectors, see collectors.
initiatives
initiativeslunar-config.yml -> initiativesType:
arrayOptional
Initiatives are used to group components together. Initiatives are associated with domains and can have tags.
For information on how to configure initiatives, see initiatives.
policies
policieslunar-config.yml -> policiesType:
arrayRequired
Policies are used to define the rules that Lunar uses to evaluate the health of components. Policies are associated with domains and can be inherited by child domains.
For information on how to configure policies, see policies.
Last updated