Skip to content
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

Fix: #18042: Updated Get-AzWebApp and Get-AzWebAppSlot to expose VirtualNetworkSubnetId property #18092

Merged
merged 5 commits into from
May 11, 2022
Merged

Conversation

Kotasudhakarreddy
Copy link
Contributor

#18042

Description

Currently, Get-AzWebApp (for one given App Service or Function App to get all details, instead of list), does not include VNet integration info. There is an attribute VirtualNetworkSubnetId, but it's null.

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

…nse when requested the WebApps under subscreption
…he response when requested the WebApps under subscreption"

This reverts commit 96a4d28.
…nse when requested the WebApps under subscreption
…he response when requested the WebApps under subscreption"

This reverts commit 96a4d28.
…lot` to expose `VirtualNetworkSubnetId` property
@wyunchi-ms
Copy link
Contributor

/azp run azure-powershell - security-tools

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants