Most of the checks in workers/ have both the logic of parameter validation/parsing/storage, return value creation, and the logic of checking whether or not the system is in the given state. This is undesirable, because the status functions can't easily be reused.
For example, packages.go contains getYumRepos() and similar functions, whereas these should be part of a separate, importable package.
A great example of the kind of separation we need is between network.go and the netutil package.
Most of the checks in
workers/
have both the logic of parameter validation/parsing/storage, return value creation, and the logic of checking whether or not the system is in the given state. This is undesirable, because the status functions can't easily be reused.For example,
packages.go
containsgetYumRepos()
and similar functions, whereas these should be part of a separate, importable package.A great example of the kind of separation we need is between
network.go
and thenetutil
package.TODO:
workers
tochecks