For reasons beyond my control we dont yet have a release pipeline for Azure Functions
However, I would like to be able to enable/disable functions on an environment via the portal
This does not seem to be possible
Is there a way around this?
How can I release a version that doesnt have this restriction?
The function app itself was created in the portal then I deployed into it
Use your local development environment to edit this Function App
Here are the steps to Enable/Disable the Function App through Portal
Steps:
Login to portal Azure Portal
Under the Subscription and the resource group go to the Function app created
Click on the App overview where you can able to see the Enable or Disable options.
Related
I'm using Azure IntelliJ Toolkit, to deploy Azure function.
This is the screenshot showing how it is getting deployed:
App Settings here is non-optional, and whatever is inserted here will override anything that already exists in Portal, as shown below:
This seems like serious bug, but wonder if there is any workaround.
Any thoughts?
Created the basic Azure Java Function Http Trigger in IntelliJ IDE and published/deployed to Azure Cloud with the default application settings:
In the Azure Portal > Function App Configuration Menu > Application Settings:
If you remove any application settings from the local IDE IntelliJ and save, the same will be in the Azure Cloud:
If you want to add more application settings, do not remove the existing ones in the IntelliJ Azure Function App Properties Window because that is local Window of the Azure Portal Function App Configuration.
For running the function project locally with the additional configuration, you have to add them in the code file of local.settings.json.
I set up Azure app service awhile ago and I am recreating an Azure App Service after a large code refactor in a new repo.
However, I am not getting the same options and I see in the original Azure App Service project.
Here is the original Azure App Service project:
Here is the new Azure App Service project:
As you can see the original one has radio options with choices for container vs code repo.
And the new one only has a dropdown for code repo options.
It's been awhile, but how did I get one App Azure app instance to have more options for deployments?
Found my answer here!
I had to go more carefully and now I see in the form where it asks what type of Instance I want.
Be sure to select Docker container.
Hi I have searched through docs on and can't quite find how to publish the developer portal through terraform. My terraform does spool a resource group with an API Management service resource but I want it to also publish the developer portal and enable CORS. Is this possible through terraform or has to be done manually after I have the rg spooled?
Updated terraform looking at the documentation here: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/api_management#host_name
There is a block for developer portal but I am not sure if this actually publishes it and also not sure what to put in the host_name. Please assist.
You can completely configure the APIM and its portal from an ARM template but you can't publish the content. There are scripts in the Github repo to do this using the rest API.
Publishing content using those scripts will work for the managed portal. If you're hosting your own version of the portal you'll have to take some additional steps, according to the migration script.
If you can get Terraform to execute NodeJs scripts, you should be able to use these to push content to the portal and publish it.
Please also check the docs that were recently added about the migration script.
I have never used terraform but I believe what you highlighted would only create a custom domain for your developer portal.
Hostname would be a custom domain, or you can use the default {apimname}.developer.azure-api.net. If you provide a custom domain for your developer portal you would have to provide a SSL certificate and also you have to have a CName for this custom domain.
I do no think the developer portal would be published Can I deploy everything through ARM templates now? The only thing that's not available is developer portal content. Everything else is available through ARM. link
Try creating an APIM manually and see what settings is it using for the developer portal in Azure Resource Explorer. Try to replicate those settings in your code.
When I create a web app for containers, then the deployment options are disabled in the Azure portal. The option is enabled if I create a regular web app and another type of resources. For web app for containers, the options was working fine till a few days back and I have no idea what triggered it to become disabled. My subscription is active and clearing browser cache, switching browsers, working with different container images, deleting and recreating resource groups, and login/logout do not help. Any suggestions?
The "Enable Deployment Options within Web App for Containers in the portal" feature was requested on feedback.azure.com and declined.
Q. Currently "Deployment Options" is only available for Web App for Windows/Linux. It would be nice if this was enabled for Web App for Containers...so I lost the simple ability to deploy from BitBucket.
A. The App Service team responded: We are declining this request since we actually discourage customers to deploy this way and recommend deployment with Container Push. That being said, there is nothing stopping you from configuring this through CLI.
To do this from the CLI, you could use this command:
az webapp deployment source config -n appname -g resourcegroupname --repo-url <gitrepo url> --branch <branch>
See Manage Web App for Containers using Azure CLI for more details.
I have created Azure Web App which OS is Docker and reproduced your issue.
From the screenshot , we can find the issue may caused by App Service Plan. I have tried to use all tiers of plan, including Isolated, but the issue is still existing. Also, for regular web app, not have the issue.
I find some updates on Azure App Service. I am not sure if the issue was caused by the updates, I recommend you to contact App Service Support Team for help.
The customer support team resolved the problem and cited "platform issue" as the cause of the problem. Now deployment options for container web apps is enabled and working again.
I was trying to create Azure Functions as provided in the help link - https://blogs.msdn.microsoft.com/webdev/2016/12/01/visual-studio-tools-for-azure-functions/
I am actually creating a Evenhub trigger to write the messages to blob storage.
When I try to run the project, I am getting an error:
"Microsoft.Azure.WebJobs.Host: Error indexing method
'Functions.DashPOCEventHub'. Microsoft.WindowsAzure.Storage: Value
cannot be null."
I have put the correct values in the appsettings.json.
Can somebody help me with this error?
Also, when I try to publish the function to Azure, the appsettings.json is not being set correctly. I cannot see the values and keys when I go into the Azure UI application settings page.
appsettings.json won't create/override your web app ApplicationSettings when you deploy. You'll need to specify the ApplicationSettings for the web app explicitly.
The reason for this is so that you can use different secrets locally (appsettings.json) from what you deploy (web app appsettings).
There is more info on appsettings.json and web app Application Settings here.
Silly John, did you update the Azure CLI when you run your Function Locally? Today is on the Azure Functions Console CLI 1.0.0-beta.97.
Probably, this update solves this issue.