Update publish-AzWebApp to support pull based deployments.

[dannysongg]

Description

Add support for pull based deployments from a URL with MSI authentication in Publish-AzWebApp. This change adds 2 parameters to enable this feature: ArchiveURL and -PullIdentity.

Notable Changes:

• Add ArchiveURL parameter
• Add PullIdentity parameter
• ArchivePath is no longer a required parameter. ArchivePath OR ArchiveURL must be provided. If both are provided, ArchivePath will be ignored

-PullIdentity Usage:

• null: MSI will not be used. This matches the existing behavior (SAS or public access)
• system: Authenticates using system assigned identity
• {client-Id}: Authenticates using provided user assigned identity

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.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Copilot]

PR Overview

This PR adds support for pull based deployments from a URL with MSI authentication in Publish-AzWebApp by introducing two new parameters: ArchiveURL and PullIdentity.

• ArchivePath is now optional and ArchiveURL is introduced as an alternative artifact source.
• The cmdlet now validates that when deploying from a URL, the deployment type is provided and restricts pull-based MSI deployments to Windows WebApps.
• Updates include changes to the cmdlet implementation, help file adjustments, test additions, and a changelog entry.

Reviewed Changes

File	Description
src/Websites/Websites/Cmdlets/WebApps/PublishAzureWebApp.cs	Updated parameters and deployment logic to support pull based deployments with MSI authentication.
src/Websites/Websites.Test/ScenarioTests/WebAppTests.cs	Added a test case for pull based deployments with MSI.
src/Websites/Websites/help/Publish-AzWebApp.md	Revised help documentation to reflect new parameters and usage.
src/Websites/Websites/ChangeLog.md	Added a changelog entry for the new MSI-based pull deployment feature.

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/Websites/Websites/Cmdlets/WebApps/PublishAzureWebApp.cs:103

• [nitpick] The variable name 'fileExtention' appears to be misspelled; consider renaming it to 'fileExtension' for clarity.

string fileExtention = Path.GetExtension(ArchivePath);

[notyashhh]

Hi @dannysongg, The way Azure pipelines run test cases is in the Playback mode. So you need to run the tests locally in 'Record' Mode. After which there will be a new file generated in SessionRecords folder that will contain the session recordings. Follow these steps: Azure Powershell Testing Docs.

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

[dannysongg]

@notyashhh session recordings have been added

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).