Closed AWahlqvist closed 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI.
Author: | AWahlqvist |
---|---|
Assignees: | - |
Labels: | `App Services`, `Service Attention`, `customer-reported`, `needs-triage`, `question` |
Milestone: | - |
@Kotasudhakarreddy did you already fix these?
@Kotasudhakarreddy did you already fix these?
No Sisira. Today I have fixed and sent for review.
Thanks @Kotasudhakarreddy I will review the PR. While you are at this - could you do me a favor if this behavior is an issue on the CLI command equivalent as well by any chance? Thank you.
Thanks @Kotasudhakarreddy I will review the PR. While you are at this - could you do me a favor if this behavior is an issue on the CLI command equivalent as well by any chance? Thank you.
Hi Sisira, CLI is working as expected for webapp and slot. I don't see any issues with az webapp config set -g MyResourceGroup -n MyUniqueApp --ftps-state FtpsOnly --slot slotName
Issue is fixed and merged for S188 release.
Description
When troubleshooting and trying to find a workaround for #14998 we tried to set FtpsState together with app settings which indeed worked. In later regression tests we found out that this cmdlet has another unexpected behavior though, it disabled AlwaysOn when it's executed, and it also doesn't seem to changed the FtpsState.
This is similar to #14884, but also points out that AlwaysOn gets disabled as well.
Steps to reproduce
Setup a web app and add a slot to it. Go the the slot and set FtpsState to something else than FtpsOnly, set AlwaysOn to On.
Then execute the following command:
Check the web app slot, the FtpsState is unchanged but AlwaysOn is turned off.
Environment data
Module versions
Debug output
This is basically a thousand lines of secrets so not sure I want to post that, but I think this is the interesting part:
The cmdlet does indeed get a response that AlwaysOn is enabled, but after this request, it's of course disabled.