#12015 Set-AzWebAppSlot incorrectly formats serverFarmId causing Service Plan not found error

[Kotasudhakarreddy]

Description

#12015

he Set-AzWebAppSlot incorrectly formats the serverFarmId before calling the REST API.

It only contains the service plan name, whereas the same for Set-AzWebApp contains the full path to the service plan.

Example :

$slot = Get-AzWebAppSlot -ResourceGroupName $resourceGroupName -Name wap-$webAppName -Slot $slotName
$slot.serverFarmId
/subscriptions/1aa9a31b-d493-4d87-9509-95785ee89b4e/resourceGroups/RGP-WWEBDEV-01/providers/Microsoft.Web/serverfarms/sla-devintpic02-03
Set-AzWebAppSlot -WebApp $slot
This fails because the REST call to update the webappslot does not provide the full serverfarmid :
"serverFarmId": "sla-devintpic02-03"

Steps to reproduce
$slot = Get-AzWebAppSlot -ResourceGroupName $resourceGroupName -Name wap-$webAppName -Slot $slotName
$slot.serverFarmId
Set-AzWebApp -WebApp $slot

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)
  • the markdown help files have been regenerated using the commands listed here

[adxsdkps]

Can one of the admins verify this patch?

[panchagnula]

LGTM

[bart-rosseel-axa]

@Kotasudhakarreddy can you sanitize the description by removing information related to our subscription ( subscribtion id, farm name, resource group names ), including deleting previous revision of the description ? Thanks in advance.