SPHealthAnalyzerRuleState error when trying to set rule that is not existent

[NikCharlebois]

With SharePointDSC (forward) if you try to set a Health Analyzer Rule that doesn't exist, you get an error. This is problematic for ReverseDSC because some rules only get created when specific Service Application are created in the farm. For example, the Health Analyzer Rule named "Could not find specified Health Analyzer Rule. Health Analyzer Rule settings will not be applied" only gets created when the Word Automation Service Application is instantiated. Therefore, a DependsOn clause should be included whenever that rule is present to ensure it waits for the Service Application to be created first.

The solution for this would be to keep a managed list of all "out-of-the-box" Health Analyzer Rules that are dependent on a specific Service Application and add custom logic to automatically append the DependsOn clauses.