Store Service Configuration
Introduction
The Infinite Scale Store service
The store service is marked for deprecation and will be removed in a later version. Its tasks will be taken over by other services. |
Configuration
Environment Variables
The store
service is configured via the following environment variables. Read the Environment Variable Types documentation for important details. Column IV
shows with which release the environment variable has been introduced.
Deprecation Info | Deprecation Version | Removal Version | Deprecation Replacement |
---|---|---|---|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
|
The store service is optional and will be removed. |
5.0 |
7.0.0 |
Name | IV | Type | Default Value | Description |
---|---|---|---|---|
|
pre5.0 |
bool |
false |
Activates tracing. |
|
pre5.0 |
string |
|
The type of tracing. Defaults to '', which is the same as 'jaeger'. Allowed tracing types are 'jaeger' and '' as of now. |
|
pre5.0 |
string |
|
The endpoint of the tracing agent. |
|
pre5.0 |
string |
|
The HTTP endpoint for sending spans directly to a collector, i.e. http://jaeger-collector:14268/api/traces. Only used if the tracing endpoint is unset. |
|
pre5.0 |
string |
|
The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'. |
|
pre5.0 |
bool |
false |
Activates pretty log output. |
|
pre5.0 |
bool |
false |
Activates colorized log output. |
|
pre5.0 |
string |
|
The path to the log file. Activates logging to this file if set. |
|
pre5.0 |
string |
127.0.0.1:9464 |
Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed. |
|
pre5.0 |
string |
|
Token to secure the metrics endpoint. |
|
pre5.0 |
bool |
false |
Enables pprof, which can be used for profiling. |
|
pre5.0 |
bool |
false |
Enables zpages, which can be used for collecting and viewing in-memory traces. |
|
pre5.0 |
string |
127.0.0.1:9460 |
The bind address of the GRPC service. |
|
pre5.0 |
string |
/var/lib/ocis/store |
The directory where the filesystem storage will store ocis settings. If not defined, the root directory derives from $OCIS_BASE_DATA_PATH:/store. |
YAML Example
-
Note that the filename shown below has been chosen on purpose.
-
See the Configuration File Naming for details when setting up your own configuration.
-
See the Notes for Environment Variables if you want to use environment variables in the yaml file.
# Autogenerated
# Filename: store-config-example.yaml
tracing:
enabled: false
type: ""
endpoint: ""
collector: ""
log:
level: ""
pretty: false
color: false
file: ""
debug:
addr: 127.0.0.1:9464
token: ""
pprof: false
zpages: false
grpc:
addr: 127.0.0.1:9460
tls: null
grpc_client_tls: null
data_path: /var/lib/ocis/store