Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Additional Scripts via Separate Config Files #116

Merged

Conversation

ricoberger
Copy link
Owner

It is now possible to define additional scripts for the exporter via separate config files. For that a new option scripts_configs was added, which can be used to set a list of files, which are containing additional script configuration.

The configuration must look as follows:

script_configs:
  - /path/to/file.yaml

The content of the additional scripts configuration file, can only contain a list of scripts, e.g.

- name: test
  command: ./examples/test.sh

Closes #115

It is now possible to define additional scripts for the exporter via
separate config files. For that a new option `scripts_configs` was
added, which can be used to set a list of files, which are containing
additional script configuration.

The configuration must look as follows:

```
script_configs:
  - /path/to/file.yaml
```

The content of the additional scripts configuration file, can only
contain a list of scripts, e.g.

```yaml
- name: test
  command: ./examples/test.sh
```
@ricoberger ricoberger added the changelog: added A new feature was added label Feb 10, 2024
@ricoberger ricoberger merged commit ebeaf94 into main Feb 10, 2024
1 check passed
@ricoberger ricoberger deleted the define-additional-scripts-via-separate-config-files branch February 10, 2024 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: added A new feature was added
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request: Allow to read script entries from separate config files
1 participant