Azure / Azure/azure-functions-core-tools

AzureWebJobs keys and values documentation

Open
#3,827 1 comment 0 reactions 0 assignees View on GitHub
doc potential-bug
Dominant language
C#
Stars
1.5k
Forks
498
Avg merge
5d 4h
Merged PRs (30d)
15

Description

### Version

4.0.5455

### Description

**UPDATE:** See comment below, issue was with `local.settings.json` configuration and poor documentation. I would like to keep this ticket to instead improve the documentation.

I am under the suspicion that the system certificate store is being ignored when using `@app.queue_trigger`

I am trying to connect to Azurite locally, and it works fine with HTTP and the HTTP connection string, but when i switch to HTTPS and run `func start` it times out after a while and gives me the following error message:

```
[2024-09-18T07:59:59.384Z] An unhandled exception has occurred. Host is shutting down.
[2024-09-18T07:59:59.384Z] Azure.Core: An error occurred while sending the request. System.Net.Http: An error occurred while sending the request. System.Net.Http: The response ended prematurely.
```

I do not want to use HTTP because i want to use `DefaultAzureCredential` (which in my case will fetch credential through managed identity) for my `QueueClient` which only works over HTTPS. However, over HTTPS the `queue_trigger` does not work. Also, fun thing to note is that i have to point my `REQUESTS_CA_BUNDLE` env var to my CA bundle to even make `QueueClient` from `azure-storage-queue` work (since i assumed it used `requests` under the hood) which is an annoyance but at least not a show stopper.

### Steps to reproduce

I provided a minimally reproducible example over here: https://github.com/linde12/azure-functions-https-trigger-bug

Instructions in README.md. In short, im able to publish messages using `QueueClient` but `@app.queue_trigger` is unable to subscribe and times out (most likely due to certificates), but works if i instead use HTTP.

Contributor guide

Open the contributing guide

Research direction

Read the linked reproduction's README.md and the issue's note about local.settings.json first. Identify which AzureWebJobs keys and values documentation needs clarification; done means the configuration guidance clearly explains the reported HTTPS and queue-trigger behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.