Added -PassThru Parameter for Compress-PSResource

[jshigetomi]

PR Summary

This pull request introduces a new PassThru parameter to the CompressPSResource cmdlet, enabling the full path of the generated .nupkg file to be returned through the pipeline. Additionally, it includes updates to the PublishHelper class to support this new functionality and adds a test case to verify the PassThru parameter's behavior.

New Feature Addition:

• src/code/CompressPSResource.cs: Added the PassThru parameter to the CompressPSResource cmdlet, allowing the full path of the .nupkg file to be passed through the pipeline. [1] [2]

Internal Code Updates:

• src/code/PublishHelper.cs: Updated the PublishHelper class to handle the new PassThru parameter, including changes to the constructor and the PackNupkg method to write the .nupkg file path to the pipeline if PassThru is specified. [1] [2]

Testing:

• test/PublishPSResourceTests/CompressPSResource.Tests.ps1: Added a new test case to ensure that the Compress-PSResource cmdlet with the -PassThru parameter correctly returns the path to the .nupkg file.

PR Context

-PassThru parameter was included in the mockup of the Compress-PSResource cmdlet but was not included in the previous PR.
This PR aims to fix that. -PassThru would be very useful for scripting Compress with Publish where the variable can be sent directly to Publish's -NupkgPath.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[alerickson]

Looks good, but -passthru should not touch the file system. It looks like right now it's displaying the pass through path but then continuing to compress the nupkg

[alerickson]

/azp PowerShell.PSResourceGet

[azure-pipelines]

Command 'PowerShell.PSResourceGet' is not supported by Azure Pipelines.

Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
• Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[alerickson]

/azp run PowerShell.PSResourceGet

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alerickson]

Nevermind! Sorry, was thinking of -WhatIf. Ignore my previous comment

[alerickson]

/azp run PowerShell.PSResourceGet

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).