I use python functions to read/write into Azure tables, unfortunately the etags are hidden. It would be quite useful to be able to access the eTags to ensure consistency of writes.2 votes
Yearly update: this is still accurate.
I have a function app set up as a private API that requires users to authenticate via Azure AD B2C to be able to make calls. My mobile app does the auth and then provides the Bearer token in the service calls.
This all works but if someone happens to browse an endpoint in a browser I don't want them to be redirected to the login page as the API is only meant to be requested from within the mobile app.
I would like an option to just deny access to the API when a request is not authorised.2 votes
This remains unscheduled, but is still a good item that we would like to get to.
If no function is present in a Function App, the “getting started” assistant is shown which allows adding a premade function. However, you can’t specify a name for the resulting function there, which is why you’ll end up with insignificant names such as “HTTPTriggerCSharp1” or “HTTPTriggerJS1”. It would be great if the user could optionally specify a function name in this dialog.2 votes
This makes sense. We’ll add it to the backlog.
Hoping we can get support added for better deployment capabilities with other languages as well as source code management. Great to see the Azure Function tooling finally make it to RTM for C#!2 votes
This remains unplanned.
My service bus will spike at the top of each hour with up to 1000+ messages to get processed immediately. It would be nice for the consumption plan to allow us to scale the # of servers to come online to be based on that queue size. Example: for 1000 messages, I would like 10 servers to come online (1 server per 100 in the queue).2 votes
We don’t currently plan to expose custom scaling logic in the consumption plan. The app service plan does allow you to specify starting scale and can auto-scale from there.
Expose StorageClientFactory or QueueProcessorFactory to enable triggering on client-side-encrypted queues
With WebJobs, a custom StorageClientFactory can set an EncryptionPolicy in the DefaultRequestOptions such that encrypted queue messages are transparently decrypted when triggering a WebJob.
Alternatively, the EncryptionPolicy can be set on a queue by queue basis using a custom QueueProcessorFactory.
If these, or a more general way to modify the JobHostConfiguration were provided, then we would be able to store the storage connection string in Azure KeyVault and use client side encryption with Azure Functions apps.1 vote
Nothing planned but still curious on this one. I think the ask is that you could decrypt on trigger. I expect trigger would work today but you’d have to have decrypt in code per execution. Is hope to decrypt before execution?
- Don't see your idea?