Azure Functions
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in other Azure services, SaaS products, and on-premises systems. With Azure Functions, your applications scale based on demand and you pay only for the resources you consume. Azure Functions provides an intuitive, browser-based user interface allowing you to create scheduled or triggered pieces of code implemented in a variety of programming languages.
-
Proxies should support backend.request.body expressions in requestOverrides
Would be great to be able to create or change the request BODY dutring request overrides processing like it is possible for headers and the method already. Expressions could override parts of the body, create a body when e.g. overriding a GET to a POST or update body parts / subparts. Even deletion of body or body parts would be usable...
17 votesThis is a great idea!
I’ve linked it up to a github issue for the same feature. https://github.com/Azure/azure-functions-host/issues/1968
-Alex
Azure Functions Team -
Access the management console for Azure Functions in an App Service Environment deployed via ILB
As it stands, Azure Functions and Web Jobs deployed in an intranet-based App Service Environment cannot be managed via the Azure portal unless the user is connected to the internal network or VPN. It appears that the advanced management console code is deployed into the App Service Environment for these services,, as the SCM host name is provisioned on the custom domain. This makes remote management difficult especially for enterprise customers.
7 votesWe are planning to make some changes to enable better access for apps hosted in ILB
-Byron
- Don't see your idea?