Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't disable an Azure function that has a hyphen in its name #1851

Closed
m3talstorm opened this issue Feb 24, 2021 · 14 comments
Closed

Can't disable an Azure function that has a hyphen in its name #1851

m3talstorm opened this issue Feb 24, 2021 · 14 comments

Comments

@m3talstorm
Copy link

m3talstorm commented Feb 24, 2021

From within the Azure Portal:

  • Create a function app (e.g some-app using App Service Plan)
  • Create a function within the app with a hyphen in the name (e.g some-app-function)
  • Navigate Functions > some-app-function and press the "Disable" button
  • You will get an error in the top right of the portal "Failed to disable function" (error will be malformed)
  • Look at the request/response it is doing, you will get:
    Message: "AppSetting with name 'AzureWebJobs.some-app-function.Disabled' is not allowed."
  • Navigate back to your Function app > Configuration
  • Add a new application setting with a value the same as above AzureWebJobs.some-app-function.Disabled
  • You will get the frontend validation message:
    App setting names can only contain letters, numbers (0-9), periods ("."), and underscores ("_")
@balag0
Copy link

balag0 commented Feb 24, 2021

Could you check if any of the other methods work for you - https://docs.microsoft.com/en-us/azure/azure-functions/disable-function

@v-anvari
Copy link

Closing this issue as there is no response. Please feel free to reach back to us or re-open this issue in case of any queries.

@m3talstorm
Copy link
Author

The bug still stands

@v-anvari
Copy link

Hi @m3talstorm , We have tried to replicate this issue but unable to reproduce it. Can you let us know if you have submitted a support request earlier? If not, can you create one, so that the support team can check the issues with your account.
Do let us know if you find any trouble.

Azure Portal > Help and support ? New support request

Thank you.

@m3talstorm
Copy link
Author

@v-anvari I have not created a support request, just this bug report.

Feel free to pass this on to the relevant team(s).

I highly doubt this would be an account-specific issue.

@v-anvari
Copy link

v-anvari commented Apr 26, 2021

Hi @m3talstorm , The support ticket is to be created through your portal, so please go ahead and create one from your account. We wouldn't be able to tell the issue if it is account specific.

Azure Portal > Help and support ? New support request

@m3talstorm
Copy link
Author

@v-anvari I do not have permissions to create a support request within our client's subscription.

I have provided as much information as I can, I cannot take any further steps.

@v-anvari v-anvari reopened this Apr 26, 2021
@v-anvari
Copy link

Thank you for the update.

@balag0 , Can you please suggest what could be done

@balag0
Copy link

balag0 commented Apr 26, 2021

@v-anvari Was the app you tested with using Windows or Linux? If we haven't done it already, could we try with both to see if we can repro it?

@v-anvari v-anvari self-assigned this Apr 27, 2021
@v-anvari
Copy link

Hi @balag0 , I am able to repro this only in linux applications. The App settings do not allow few of the special characters for linux Apps.

Windows:

image

image

App settings for windows : image

Linux :

image

App settings for Linux image

@v-anvari v-anvari added this to the Triaged milestone May 4, 2021
@v-anvari
Copy link

Hi @m3talstorm , This issue has been identified and is being investigated for fix. For now, this issue is by design for Linux and is being discussed on the fix.

Investigation incident - https://portal.microsofticm.com/imp/v3/incidents/details/242098161/home

Closing this issue as further updates will be provided in the tracking incident, please feel free to reach back to us in case of any further queries related to this issue

@v-anvari v-anvari removed this from the Triaged milestone Jun 16, 2021
@scott-alvis
Copy link

Why is this closed it still an open issue?

@ormu5
Copy link

ormu5 commented Dec 31, 2022

Interestingly, I deployed the following with terraform in my linux function app settings:

"AzureWebJobs.fetch-and-publish.Disabled" = "true",
"AzureWebJobs.subscribe-and-send.Disabled" = "false",
"AzureWebJobs.receive-and-insert.Disabled" = "false",

and it succeeded in disabling 'fetch-and-publish'.

Follow-up az cli commands, though, led to a vague "Operation returned an invalid status 'Bad Request'" behind which was the subject error:

azure.core.exceptions.HttpResponseError: Operation returned an invalid status 'Bad Request'
Content: {"Code":"BadRequest","Message":"AppSetting with name 'AzureWebJobs.fetch-and-publish.Disabled' is not allowed.","Target":null,"Details":[{"Message":"AppSetting with name 'AzureWebJobs.fetch-and-publish.Disabled' is not allowed."},{"Code":"BadRequest"},{"ErrorEntity":{"ExtendedCode":"04072","MessageTemplate":"AppSetting with name '{0}' is not allowed.","Parameters":["AzureWebJobs.fetch-and-publish.Disabled"],"Code":"BadRequest","Message":"AppSetting with name 'AzureWebJobs.fetch-and-publish.Disabled' is not allowed."}}],"Innererror":null}

@ssssssseb
Copy link

Just ran into this issue as well. Please fix, Azure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants