Hot reload of configuration changes should validate changes #11817
Description
Is your feature request related to a problem? Please describe.
We can hot reload the collector with new configuration. However, this new configuration may fail validation.
Example:
2024-12-06T11:10:22.536-0800 info [email protected]/collector.go:328 Received signal from OS {"signal": "hangup"}
2024-12-06T11:10:22.537-0800 warn [email protected]/collector.go:237 Config updated, restart service
2024-12-06T11:10:22.537-0800 info [email protected]/service.go:303 Starting shutdown...
2024-12-06T11:10:22.537-0800 info adapter/receiver.go:68 Stopping stanza receiver {"kind": "receiver", "name": "filelog", "data_type": "logs"}
2024-12-06T11:10:22.537-0800 info extensions/extensions.go:66 Stopping extensions...
2024-12-06T11:10:22.537-0800 info [email protected]/service.go:317 Shutdown complete.
Error: failed to setup configuration components: invalid configuration: service::pipelines::logs: references receiver "filelog/foo" which is not configured
2024/12/06 11:10:22 collector server run finished with error: failed to setup configuration components: invalid configuration: service::pipelines::logs: references receiver "filelog/foo" which is not configured
Describe the solution you'd like
The collector should run validation of the incoming configuration. The collector should continue to run with the old configuration instead of failing.