Azure / Azure/azure-functions-dotnet-worker
[Question] Two autocomplete settings, which has precedence?
- Dominant language
- C#
- Stars
- 466
- Forks
- 215
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
# Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, [#46445](https://github.com/Azure/azure-sdk-for-net/issues/46445).
### Please be aware that @arghasen93 is the author of the original issue and include them for any questions or replies.
## Details
### Library name and version
Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.22.0
### Describe the bug
What is the meaning of having host.json file consisting "autocompletemessage" property having value "false" and also explicitly have to set "AutoCompleteMessages" to false in "ServiceBusTriggerAttribute" class. And I have also observed that it's not respecting "clientRetryOptions".
### Expected behavior
If autocompletemessage in "host.json" file has the value false then azure function should not complete and remove the messages from Azure Service Bus topic
### Actual behavior
Even though autocompletemessage in "host.json" to false it's completing and removing the messages from Azure Service Bus
### Reproduction Steps
Create an Azure function based on servicebus trigger in dotnet-isolated (.NET 8) and set "autocompletemessage" to false in host.json file in servicebus extension
### Environment
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the .NET 8 isolated Azure Function scenario using the host.json autocompletemessage setting and the ServiceBusTriggerAttribute AutoCompleteMessages setting. Determine which setting takes precedence and whether clientRetryOptions is honored; done means the precedence and resulting message-completion behavior are established or corrected and can be verified against the reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100