-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy path__init__.py
More file actions
133 lines (102 loc) · 3.45 KB
/
__init__.py
File metadata and controls
133 lines (102 loc) · 3.45 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
# Copyright 2023 Cognite AS
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
"""
Module containing tools for loading and verifying config files.
Configs are described as ``dataclass`` es, and use the ``BaseConfig`` class as a superclass to get a few things
built-in: config version, Cognite project and logging. Use type hints to specify types, use the ``Optional`` type to
specify that a config parameter is optional, and give the attribute a value to give it a default.
For example, a config class for an extractor may look like the following:
.. code-block:: python
@dataclass
class ExtractorConfig:
parallelism: int = 10
state_store: Optional[StateStoreConfig]
...
@dataclass
class SourceConfig:
host: str
username: str
password: str
...
@dataclass
class MyConfig(BaseConfig):
extractor: ExtractorConfig
source: SourceConfig
You can then load a YAML file into this dataclass with the `load_yaml` function:
.. code-block:: python
with open("config.yaml") as infile:
config: MyConfig = load_yaml(infile, MyConfig)
The config object can additionally do several things, such as:
Creating a ``CogniteClient`` based on the config:
.. code-block:: python
client = config.cognite.get_cognite_client("my-client")
Setup the logging according to the config:
.. code-block:: python
config.logger.setup_logging()
Start and stop threads to automatically push all the prometheus metrics in the default prometheus registry to the
configured push-gateways:
.. code-block:: python
config.metrics.start_pushers(client)
# Extractor code
config.metrics.stop_pushers()
Get a state store object as configured:
.. code-block:: python
states = config.extractor.state_store.create_state_store()
However, all of these things will be automatically done for you if you are using the base Extractor class.
"""
from cognite.extractorutils.exceptions import InvalidConfigError
from .elements import (
AuthenticatorConfig,
BaseConfig,
CastableInt,
CertificateConfig,
CogniteConfig,
ConfigType,
ConnectionConfig,
EitherIdConfig,
FileSizeConfig,
LocalStateStoreConfig,
LoggingConfig,
MetricsConfig,
PortNumber,
RawDestinationConfig,
RawStateStoreConfig,
StateStoreConfig,
TimeIntervalConfig,
)
from .loaders import ConfigResolver, KeyVaultAuthenticationMethod, KeyVaultLoader, load_yaml, load_yaml_dict
__all__ = [
"AuthenticatorConfig",
"BaseConfig",
"CastableInt",
"CertificateConfig",
"CogniteConfig",
"ConfigResolver",
"ConfigType",
"ConnectionConfig",
"EitherIdConfig",
"FileSizeConfig",
"KeyVaultAuthenticationMethod",
"KeyVaultLoader",
"LocalStateStoreConfig",
"LoggingConfig",
"MetricsConfig",
"PortNumber",
"RawDestinationConfig",
"RawStateStoreConfig",
"StateStoreConfig",
"TimeIntervalConfig",
"load_yaml",
"load_yaml_dict",
]