Configuration
Configuring Tarmac
Tarmac supports multiple configuration sources such as Environment Variables, JSON files, or using HashiCorp Consul. All of these configuration options can also exist together to provide both static and dynamic configurations.
When using Environment Variables, all configurations are prefixed with APP_
. The list below will show both Environment and Consul/JSON format for configuration.
Environment Variable | Consul/JSON | Type | Description |
---|---|---|---|
|
|
| Enable the HTTPS Listener (default: |
|
|
| Define the HTTP/HTTPS Listener address (default: |
|
|
| Frequency in seconds which Consul configuration will be refreshed (default: |
|
|
| Enable Consul based configuration (default: |
|
|
| Consul address (i.e. |
|
|
| Key path for app specific consul configuration |
|
| Indicator to reflect whether Consul config was loaded | |
|
|
| Enable debug logging |
|
|
| Enable trace logging |
|
|
| Disable all logging |
|
|
| Certificate File Path (i.e. |
|
|
| Key File Path (i.e. |
|
|
| Certificate Authority Bundle File Path (i.e |
|
|
| When defined will disable Client Cert validation for m-TLS authentication |
|
|
| Path and Filename of the WASM Function to execute (Default: |
|
|
| Path to Service configuration for multi-function services (Default: |
|
|
| Number of WASM function instances to create (Default: |
|
|
| Enable PProf Collection HTTP end-points |
|
|
| Enable the KV Store |
|
|
| Select KV Store to use (Options: |
|
|
| Enable the SQL Store |
|
|
| Select SQL Store to use (Options: |
Consul Format
When using Consul the consul_keys_prefix
should be the path to a key with a JSON string
as the value. For example, a key of tarmac/config
will have a value of {"from_consul":true}
.
Last updated