How to get useful error in the PAC CLi

[h-karthik12]

Deploying OrganizationSettingsEditor to atest with without Environment Setting File
pac solution import --path '/home/admin2024/myagent/_work/1/DeploymentArtifact/ManagedSolutions/OrganizationSettingsEditor/SolutionZipFiles/OrganizationSettingsEditor_managed.zip'--async true --force-overwrite false --publish-changes true --skip-dependency-check false --convert-to-managed true --max-async-wait-time 60 --activate-plugins true --skip-lower-version true --stage-and-upgrade true
Connected as ***
Microsoft PowerPlatform CLI
Version: 1.38.3+g63c17ef
Online documentation: https://aka.ms/PowerPlatformCLI
Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions

Error: The value passed to '--path' is invalid. The file '/home/admin2024/myagent/_work/1/DeploymentArtifact/ManagedSolutions/OrganizationSettingsEditor/SolutionZipFiles/OrganizationSettingsEditor_managed.zip' could not be found.

Usage: pac solution import [--environment] [--path] [--activate-plugins] [--force-overwrite] [--skip-dependency-check] [--import-as-holding] [--stage-and-upgrade] [--publish-changes] [--convert-to-managed] [--async] [--max-async-wait-time] [--settings-file] [--skip-lower-version]

  --environment               Specifies the target Dataverse. The value may be a Guid or absolute https URL. When not specified, the active organization selected for the current auth profile will be used. (alias: -env)
  --path                      Path to solution zip file. If not specified, assumes the current folder is a cdsproj project. (alias: -p)
  --activate-plugins          Activate plug-ins and workflows on the solution. (alias: -ap)
  --force-overwrite           Force an overwrite of unmanaged customizations (alias: -f)
  --skip-dependency-check     Skip dependency check against dependencies flagged as product update (alias: -s)
  --import-as-holding         Import the solution as a holding solution. (alias: -h)
  --stage-and-upgrade         Import and upgrade the solution. (alias: -up)
  --publish-changes           Publish your changes upon a successful import. (alias: -pc)
  --convert-to-managed        Convert to a managed solution. (alias: -cm)
 --async                     Imports the solution asynchronously. (alias: -a)
  --max-async-wait-time       Max asynchronous wait time in minutes. The default value is 60 minutes. (alias: -wt)
  --settings-file             The .json file with the deployment settings for connection references and environment variables.
  --skip-lower-version        Skip solution import if same or higher version is present in current environment. (alias: -slv)

Deploying OrganizationSettingsEditor to atest Completed

This will not give exit code and it passes without error and proceeds to next

Deploying TestBase to atest with Environment Setting File

Processing asynchronous operation... execution time: 00:00:08 and 0.23% of max time allotted

Processing asynchronous operation... execution time: 00:00:12 and 0.34% of max time allotted

Processing asynchronous operation... execution time: 00:00:16 and 0.46% of max time allotted

Processing asynchronous operation... execution time: 00:00:20 and 0.57% of max time allotted

Processing asynchronous operation... execution time: 00:00:24 and 0.68% of max time allotted

Processing asynchronous operation... execution time: 00:00:28 and 0.80% of max time allotted

Processing asynchronous operation... execution time: 00:00:32 and 0.91% of max time allotted

Asynchronous operation 806b7be9-a104-f011-bae2-00224809e1cd failed within 00:00:36.8590341.

The reason given was: ImportAsHolding failed with exception :Solution manifest import: FAILURE: The following solution cannot be imported: TestBase. Some dependencies are missing. The missing dependencies are : <MissingDependencies><MissingDependency><Required type="connectionreference" displayName="new_dataverse" solution="Active" id.connectionreferencelogicalname="new_dataverse" /><Dependent type="29" displayName="testing" id="{f8443a69-9604-f011-bae2-002248090efa}" /></MissingDependency></MissingDependencies> , ProductUpdatesOnly : False
Microsoft PowerPlatform CLI
Version: 1.38.3+g63c17ef
Online documentation: https://aka.ms/PowerPlatformCLI
Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions

Error: The async operation completed with a statuscode of Failed.

##[error]Deployment failed with exit code 1

This will give us the error code. Why this type of differenet behaviour does this have any standard objects created when error occurs so we can use it with $_