EXO test - OPA output function

[ober758181]

🐛 Summary

I am getting the following error when trying to run the exchange online test:

unable to parse input: yaml: line 3669: did not find expected ',' or ']'
Fatal Error involving the OPA output function.
Ending ScubaGear execution. See the exception message for more details: Cannot bind argument to parameter
'InputObject' because it is null.
At C:\Users\xxx\Downloads\ScubaGear-1.0.0\ScubaGear-1.0.0\PowerShell\ScubaGear\Modules\Orchestrator.psm1:651
char:13
throw $InvokeRegoErrorMessage

   CategoryInfo          : OperationStopped: (Fatal Error inv...use it is null.:String) [], RuntimeException
   FullyQualifiedErrorId : Fatal Error involving the OPA output function.
               Ending ScubaGear execution. See the exception message for more details: Cannot bind argument to parame
  ter 'InputObject' because it is null.


## To reproduce ##

Run the following to reproduce: 
Invoke-SCuBA -ProductNames exo
## Expected behavior ##

I expected the output. The other tests worked great!

## Any helpful log output or screenshots ##
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.22000.2600
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22000.2600
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

![image](https://github.com/cisagov/ScubaGear/assets/24191475/57076ee9-4a74-4e54-92c3-613ace7dacaa)

[gdasher]

Thanks for the bug report! A few questions:

1. I don't see the line about "unable to parse input: yaml: line 3669: did not find expected ',' or ']'" in the image you included. Is that right above where you cut off the image?

2. Do you get any of the files (TestResults.json, TestResults.csv, ProviderSettingsExport.json) produced when you run the tool for Exo?

3. Assuming it is created, can you share a snippet from around line 3669 of ProviderSettingsExport.json, assuming its not sensitive? We've seen a few errors like this in the past with how the escaping plays out, for example. I believe the error you cited is coming from opa failing to parse the tenant state.

[ober758181]

1. Hey Grant, here is another screenshot: [image: image.png] 2. Yes, I got: ProviderSettingsExport.json 3. Sure: "ExceptIfManagerAddresses": null,

…

On Fri, Dec 29, 2023 at 11:55 PM Grant Dasher ***@***.***> wrote: Thanks for the bug report! A few questions: 1. I don't see the line about "unable to parse input: yaml: line 3669: did not find expected ',' or ']'" in the image you included. Is that right above where you cut off the image? 2. Do you get any of the files (TestResults.json, TestResults.csv, ProviderSettingsExport.json) produced when you run the tool for Exo? 3. Assuming it is created, can you share a snippet from around *line 3669* of ProviderSettingsExport.json, assuming its not sensitive? We've seen a few errors like this in the past with how the escaping plays out, for example. I believe the error you cited is coming from opa failing to parse the tenant state. — Reply to this email directly, view it on GitHub <#770 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFYSD477LODJPLJD7MFCQGTYL6NF3AVCNFSM6AAAAABBFYBWFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGQ2TENBVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[schrolla]

@ober758181 We had another report of this sort of error and it was due to the way we handle backslashes ('') in some of our code interacting with a transport rule condition (or some other setting) that ends with a backslash. You can see issue #808 for a possible workaround and we've noted the bug for review and fixes in #818.