-
Notifications
You must be signed in to change notification settings - Fork 4k
Azure Firewall Packet Capture Cmdlet Update [public preview feature] #28163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-network-2024-10-01
Are you sure you want to change the base?
Azure Firewall Packet Capture Cmdlet Update [public preview feature] #28163
Conversation
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Please update the Changelog. |
LGTM |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Need this checked in before 7/15 branch cut so please let me know, will make suggested changes asap |
Hi @nikhilpadhye1, The PR change looks fine but the CI check failed. I'll see what's wrong in the CI checks. |
@YanaXu please let me know whats needed to fix the CI check. Will make those changes ASAP. As mentioned previously looking to have this merged by 7/15 for a branch cut |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @nikhilpadhye1 , the CI failed in building the module. Please check it locally with
|
Description
Added support for Operation field which allows the invoke-packetcapture cmdlet to run start/status/stop operations. Additionally fixed the return type by introducing the PSAzurePacketCaptureResponse object which will return a status code and message which explains the result of the ran operation.
Updated the fields for the packet capture parameters to be inline with the changes
Updated tests and generated help files to be up to date with the latest changes
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.