We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now the configuration in the compliance tests is hard coded in the test targets. Example: https://github.com/prometheus/compliance/blob/main/remote_write_sender/targets/otel.go#L16
It would be useful if it was possible to specify the configuration from a file using command line parameters.
If the configuration is not in a file, it should fall back to the to the hard coded version.
The reason why we need this is because depending on the version of the target under test, we need to use different configurations.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Right now the configuration in the compliance tests is hard coded in the test targets. Example: https://github.com/prometheus/compliance/blob/main/remote_write_sender/targets/otel.go#L16
It would be useful if it was possible to specify the configuration from a file using command line parameters.
If the configuration is not in a file, it should fall back to the to the hard coded version.
The reason why we need this is because depending on the version of the target under test, we need to use different configurations.
The text was updated successfully, but these errors were encountered: