Description of problem:
The record package is currently is the place where the gather-functions are actually run and it also responsible for storing the output. This is to much responsibility for one component and we have the Gatherer which only collects the gather-functions but not actually runs them.
So the recordpackage should only care about the storing of the data and not actually creating it, and the Gatherer should be responsible for managing the the gather-functions. (by managing I mean: deciding which to run, handling errors for gathering, [in the future] syncing up the multi-threaded workloads of the gather-functions)
This will allow us to have greater control over how the gathering is done, and will simplify the code base.
Also insightsclient is somewhat linked to GatherClusterVersion, it undoes this link.
Furthermore makes the gathering configurable via the yaml config.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Documentation in the PR describes how to configure gathering via yaml config with local IO. I understand it as there need to be other steps to utilize it in/use it in support config.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.