webapp:Unable to set WebApp Slot logging using az webapp log config --ids [webapp slot id]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug

The command “az webapp log config” when used with the parameter “–ids [appServiceSlotID]” configure the main AppService instead of the specified AppService Slot.

To Reproduce

1. Create a Resource Group, say “resourceGroupName”.
2. Create an AppService in the newly created Resource Group, say “appServiceName”.
3. Add an AppService Slot to the newly created AppService, say “appServiceSlotName”.
4. Run the following command:

az webapp log config \
--docker-container-logging "filesystem" \
--ids "/subscriptions/[subscriptionID]/resourceGroups/[resourceGroupName]/providers/Microsoft.Web/sites/[appServiceName]/slots/[appServiceSlotName]"

Expected behavior

The specified AppService Slot/AppService Logs is enabled with the following default parameters:

• Application Logging: filesystem
• Quota (MB): 100
• Retention Period (Days): 3

Observed behavior

The AppService/AppService Logs is enabled with the following default parameters:

• Application Logging: filesystem
• Quota (MB): 100
• Retention Period (Days): 3

Environment summary

Install Method: apt CLI version: 2.27. OS version : Ubuntu 20.04.2 LTS Shell Type: bash

Additional context

The following equivalent command works as expected:

az webapp log config \
--docker-container-logging "filesystem" \
--resouce-group [resourceGroupName] \
--name [appServiceName] \
--slot [appServiceSlotName]

[Kotasudhakarreddy]

@PatrickMessierGoC Agree with your suggestion. But this is not the problem with only webapp this is the same behavior with all the other azure resources too. So we will take it into CLI core team to handle this at root level instead of individual module level.

[PatrickMessierGoC]

As mentionned on Sept 10th, I now understand that. My point is that - based on the command documentation on the [–ids] parameter - “It should be a complete resource ID containing all information of ‘Resource Id’ arguments. You should provide either --ids or other ‘Resource Id’ arguments.” make me (and probably some other people) believe that we can either provide a full resource ID (an App Service Slot has a Resource ID) or the other resource Id arguments which are namely the [–subscription], the [–resource-group], the App Service [–name], and the [–slot] name. In other words, we should not mix [–Ids] and [–slot] parameters.

A meaningfull warning or error message would have been appreciated. That’s all.