Add --ignore-warnings to Export command

[Trenly]

• I have signed the Contributor License Agreement.
• This pull request is related to an issue.
  • Export should allow suppressing missing source warnings #4213

Manually validated output files remained the same.

---

Microsoft Reviewers: Open in CodeFlow

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yao-msft]

Just leave my thoughts here. In the future, if we want to filter the output, we should do a refactor and do it in reporter level. So we don't need to check every place. Something like Reporter.DisableReportLevel(Level::Warning), then reporter will no longer output for warning level.

[Trenly]

Just leave my thoughts here. In the future, if we want to filter the output, we should do a refactor and do it in reporter level. So we don't need to check every place. Something like Reporter.DisableReportLevel(Level::Warning), then reporter will no longer output for warning level.

Good point; I can try taking a look into that (in a separate PR), though it may be above my skill level

[yao-msft]

Good point; I can try taking a look into that (in a separate PR), though it may be above my skill level

If we can do in the Reporter level, I would discard this pr. This one only disable the warning in this specific workflow task, it will not ignore warnings from previous steps in ExportCommand like HandleSearchResultFailures

And we don't need to do spot checks at multiple places. the code will be cleaner.

[Trenly]

If we can do it at the reporter level, I would revert these changes as part of the PR to handle the reporter refactor, since with that refactor the --ignore-warnings arg should likely be added to the common args list rather than individual commands anyways

I know that there are other areas like ValidateCommand which would also need to be cleaned up anyways

[yao-msft]

If we can do it at the reporter level, I would revert these changes as part of the PR to handle the reporter refactor, since with that refactor the --ignore-warnings arg should likely be added to the common args list rather than individual commands anyways

That's fine too.

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Trenly]

Failed ConfigureFromHttpsConfigurationFile [282 ms]
  Error Message:
     Expected: 0
  But was:  1
  Stack Trace:
     at AppInstallerCLIE2ETests.ConfigureCommand.ConfigureFromHttpsConfigurationFile() in D:\a\1\s\src\AppInstallerCLIE2ETests\ConfigureCommand.cs:line 182

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).