Remove opamp remote config dir readable validation #1385
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
opamp
extension configuration was added tosumologic.yaml
as part of #1343. The extension is not enabled by default. This initial configuration is intended to aid in the reliability and formatting of setting up remote management via the installation script (install.sh
). Unfortunately, the extension validation currently ensures theremote_configuration_directory
is readable, causing regular installations to fail, for example:This pull-request removes this validation, as the extension does this as part of effective configuration loading, see:
sumologic-otel-collector/pkg/extension/opampextension/opamp_agent.go
Lines 318 to 321 in 6f3f290
We will need to do a release after merging this pull-request (if accepted) in order to fix standard collector installation.
Alternatively, we can remove
opamp
extension configuration fromsumologic.yaml
, however, we still need a release and we lose the extra reliability and formatting of setting up remote management via the installation script.