Web App update method is not updating resource configuration

[sdsubhajitdas]

• Package Name: @azure/arm-appservice
• Package Version: 15.0.0
• Operating system: macOS Sonoma Version 14.5
• nodejs
  • version: 20.14.0
• browser
  • name/version:
• typescript
  • version:
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://learn.microsoft.com

Describe the bug
I have an Azure Web App where I am using the following code to get the Web App configuration

const { WebSiteManagementClient } = require("@azure/arm-appservice");
const { DefaultAzureCredential } = require("@azure/identity");
const util = require("util");

async function main() {
  const subscriptionId = "<subscription_id>";
  const client = new WebSiteManagementClient(new DefaultAzureCredential(), subscriptionId);

  let webAppConfiguration = await client.webApps.getConfiguration("<resource_group>", "<web_app_name>");
  console.log(util.inspect(webAppConfiguration, { depth: null }));
}
main();

In the webAppConfiguration, I see that my ftpsState field value is disabled.

Now I am trying to use the following code to update the Web App configuration

const { WebSiteManagementClient } = require("@azure/arm-appservice");
const { DefaultAzureCredential } = require("@azure/identity");
const util = require("util");

async function main() {
  const subscriptionId = "<subscription_id>";
  const client = new WebSiteManagementClient(new DefaultAzureCredential(), subscriptionId);

  await client.webApps.update("<resource_group>", "<web_app_name>", {
    siteConfig: { ftpsState: "Disabled" },
  });

  let webAppConfiguration = await client.webApps.getConfiguration("<resource_group>", "<web_app_name>");
  console.log(util.inspect(webAppConfiguration, { depth: null }));
}
main();

After updating the configuration and checking the output I still see that in the webAppConfiguration object ftpsState value is still set to disabled.

To Reproduce
Steps to reproduce the behavior:
1.

Expected behavior
I expected the webApps.update function to update the Web App configuration with the value Disabled for the ftpsState field. Instead, I see the value is still set to disabled.

Screenshots

Additional context
When I first tried to update the configuration of the Web App I called the update method with the following

{
    siteConfig: { ftpsState: "disabled" }
}

I later realized the allowed value was Disabled instead of disabled.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp @AzureAppServiceCLI.

[kazrael2119]

will check

[kazrael2119]

@sdsubhajitdas , appservice has a api named updateConfiguration(),
could you use that? I think client.webApps.update() may not work for configuration.
as when I called webApps.get(), the ftpsState from the result is null, but I calledwebApps.getConfiguration(), the ftpsState is disabled.
here is my code to test:

    const result=await client.webApps.getConfiguration(resourceGroupName,"czwapp");
    console.log(result.ftpsState);

    const res=await client.webApps.update(resourceGroupName,"czwapp",
      {
        siteConfig:{ftpsState: "AllAllowed"} 
      }
    );
    console.log(res.siteConfig?.ftpsState)

    const res1=await client.webApps.updateConfiguration(resourceGroupName,"czwapp",
      {
        ftpsState: "Disabled"
      }
    )
    console.log(res1.ftpsState)

and the result is :

disabled
null
Disabled

[sdsubhajitdas]

Thanks for the response @kazrael2119 .
I tried the updateConfiguration API and yes it works.
From your testing code, I can see that you are transitioning from AllAllowed -> Disabled, which also works for me.
But I am trying to transition from disabled -> Disabled state.

[kazrael2119]

Thanks for the response @kazrael2119 . I tried the updateConfiguration API and yes it works. From your testing code, I can see that you are transitioning from AllAllowed -> Disabled, which also works for me. But I am trying to transition from disabled -> Disabled state.

you can ignore

const res=await client.webApps.update(resourceGroupName,"czwapp",
      {
        siteConfig:{ftpsState: "AllAllowed"} 
      }
    );

this one is tell you that webapp.update() doesn't work. the ftpsState result from webApps.get() is null and I try to update it as AllAllowed but it is still null.
you can see first I get the configuration and the ftpsState is disabled, and then I call the updateConfiguration(), the result is changed to Disabled

[sdsubhajitdas]

@kazrael2119

Here is my code to test

  const client = new WebSiteManagementClient(new DefaultAzureCredential(), subscriptionId);

  let webAppConfiguration = await client.webApps.getConfiguration(resourceGroup, webAppName);
  console.log("Web App Configuration Before Update");
  console.log(webAppConfiguration.ftpsState);

  console.log("Updating configuration...");
  let result = await client.webApps.updateConfiguration(resourceGroup, webAppName, {
    ftpsState: "Disabled"
  });
  console.log(result.ftpsState);

  webAppConfiguration = await client.webApps.getConfiguration(resourceGroup, webAppName);
  console.log("Web App Configuration After Update");
  console.log(webAppConfiguration.ftpsState);

and the output for the following

Web App Configuration Before Update
disabled
Updating configuration...
disabled
Web App Configuration After Update
disabled

The state is not changing from disabled to Disabled.

[kazrael2119]

I tried to debug this case and I found that the request body is Disabled but the response is still diasbled. I think this should be a service issue.

Normally, on portal we can select three value for ftps states:

but when I updated the status as disabled, this value is null on portal：

I guess in the server side does not distinguish between uppercase and lowercase, but supports the use of lowercase if using sdks

[kazrael2119]

Add Service attention for awareness

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp @AzureAppServiceCLI.

[qiaozha]

@sdsubhajitdas since this is a service backend issue, could you open a support ticket to get better support from them directly https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request, thank you.

[github-actions]

Hi @sdsubhajitdas. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[github-actions]

Hi @sdsubhajitdas, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!