You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,24 @@ Dependencies that are needed to build and are not being downloaded via gradle:
22
22
23
23
`./gradlew build`
24
24
25
+
The build can be further customized via different build profiles. Available profiles are:
26
+
27
+
* default - Default build including tests. Used by default.
28
+
* minimal - Minimal build without tests for fast local builds
29
+
* deploy - Full build including tests, packaging of mapping-plugin-core, and
30
+
deployment to maven-central. This build profile is supposed to be
31
+
used inside a CI environment, as it requires further configuration,
32
+
i.e., credentials for deployment.
33
+
34
+
The different build profiles can be activated via:
35
+
36
+
`./gradlew build -PbuildProfile=minimal`
37
+
25
38
### Python Location
26
39
27
-
The mapping-service supports plugins running Python code. To provide basic testing for this feature, some tests require configured Python in order to be executed.
40
+
The mapping-service supports plugins running Python code. To provide basic testing for this feature, some tests require configured Python in order to be executable.
28
41
While at runtime, the Python executable is configured in application.properties, at build time the Python location may differ depending on the build environment.
29
-
By default, '/usr/bin/python' is assumed as Python location. If you are using a different Python installation, e.g., under Windows or MacOS, you may either modify
42
+
By default, '/usr/bin/python3' is assumed as Python location. If you are using a different Python installation, e.g., under Windows or MacOS, you may either modify
30
43
'build.gradle' (look out for pythonExecutable) or you provide the Python executable as command line argument, e.g.,
31
44
32
45
```
@@ -43,10 +56,15 @@ and modify it according to your needs. Espacially the following properties (at t
43
56
| spring.datasource.url | The path points to the location of the database in which your configured mappings are stored. For production use it is not recommended to use the pre-configured H2 database! | jdbc:h2:file:/tmp/mapping-service/database |
44
57
| mapping-service.pythonExecutable | The path to your local Python executable. The default uses the pythonExecutable system property provided via -DpythonExecutable= or file:///usr/bin/python3 if no such system property is provided. | ${pythonExecutable:'file:///usr/bin/python3'} |
45
58
| mapping-service.pluginLocation | The local folder from where plugins are loaded. The folder will be created on startup if it does not exist. | None |
59
+
| mapping-service.codeLocation | The local folder where plugins can checkout code from GitHub. For Python-based plugins, also the virtual env is created in this folder. The folder will be created on startup if it does not exist. | None |
46
60
| mapping-service.mappingSchemasLocation | The local folder where the mapping files are stored. The folder will be created on startup if it does not exist. | None |
47
61
| mapping-service.jobOutput | The local folder where asynchronous mapping execution job outputs are stored. The folder will be created on startup if it does not exist. | None |
48
62
| mapping-service.packagesToScan | Packages scanned for mapping plugins in addition to plugins located in mapping-service.pluginLocation. Typically, this property has not the be changed. | edu.kit.datamanager.mappingservice.plugins.impl |
49
63
| mapping-service.executionTimeout | The timeout in seconds a plugin process, i.e., Python of Shell, may take before it is assumed to be stale. | 30 |
64
+
| mapping-service.authEnabled | Defines if authentication is enabled or not. If enabled, additional keycloak configuration is required. | false |
65
+
| mapping-service.mappingAdminRole | Defines the user role which must be present to be able to administrate the mapping service, i.e., add or remove mappings. | MAPPING_ADMIN |
66
+
| management.metrics.export.prometheus.enabled | Enables or disabled capturing of prometheus metrics. | true |
67
+
| management.endpoint.metrics.enabled | Enables or disabled the metrics actuator endpoint. This is only needed, if metrics are captured at all. | true |
0 commit comments