Secret not found error not reported in Output status

[aslafy-z]

trafficstars

Describe the bug: If an Output references a wrong or inexistent secret, the error is not reported into the Output's status.

Expected behaviour: Output.status.active is set to false, Flow.status.active is set to false. Output should reference the error message in its status, and Flow should get, if there was a single output configured in it, status.active: false too.

Steps to reproduce the bug:

• Create an Output that references a non existing secret.
• Create a Flow that references the previous Output.
• Check Output/Flow status

Environment details:

• logging-operator version (e.g. 2.1.1): 3.17.10

/kind bug

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

[pepov]

Idea: the validation reconciler runs after the configuration is generated so in theory we can already depend on the loggingResources variable which contains all the outputs to also register and associate the error with the given outputs and let the validation reconciler report it in the status.