Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Function [XYZ]: cannot find value named 'ServiceBusConnection' in local.settings.json that matches 'connection' property set on 'serviceBusTrigger' #32840

Closed
petrkoutnycz opened this issue Dec 2, 2022 · 8 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Functions issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@petrkoutnycz
Copy link

Library name and version

microsoft.azure.webjobs.extensions.servicebus 5.8.1

Describe the bug

I was trying to enable Managed Identity together with ServiceBusTrigger in my Azure Function according to the official guide here: https://learn.microsoft.com/en-us/azure/azure-functions/functions-identity-based-connections-tutorial-2.

Expected behavior

There is no MSBuild warning regarding missing setting in local.settings.json when using Managed Identity for Azure Functions.

Actual behavior

There is a warning Function [XYZ]: cannot find value named 'ServiceBusConnection' in local.settings.json that matches 'connection' property set on 'serviceBusTrigger' . This warning is misleading since according to the guide, there should not even be a setting like that since there is a ServiceBusConnection__fullyQualifiedNamespace present.

Reproduction Steps

Prepare an Azure Function based on the official page here: https://learn.microsoft.com/en-us/azure/azure-functions/functions-identity-based-connections-tutorial-2.

Environment

  • macOS Ventura 13.0.1
  • .NET SDK 6.0.403
  • IDE: both Rider and Visual Studio
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 2, 2022
@azure-sdk
Copy link
Collaborator

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Service Bus:0.56548464,Functions:0.3949278,Azure.Identity:0.03112505'

@michaeldwood
Copy link

This is also true for any function trigger that supports the "__fullyQualifiedNamespace" connection property (hack).

@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. Functions needs-team-attention This issue needs attention from Azure service team or SDK team labels Dec 2, 2022
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Dec 2, 2022
@jsquire
Copy link
Member

jsquire commented Dec 2, 2022

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@JoshLove-msft
Copy link
Member

I believe the issue here is related to the version of the Core Tools being used. Can you try using the latest?

@JoshLove-msft JoshLove-msft added the needs-author-feedback More information is needed from author to address the issue. label Dec 7, 2022
@ghost ghost removed the needs-team-attention This issue needs attention from Azure service team or SDK team label Dec 7, 2022
@petrkoutnycz
Copy link
Author

@JoshLove-msft will give it a shot, thanks

@ghost ghost added needs-team-attention This issue needs attention from Azure service team or SDK team and removed needs-author-feedback More information is needed from author to address the issue. labels Dec 12, 2022
@JoshLove-msft JoshLove-msft added the issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. label Dec 13, 2022
@ghost
Copy link

ghost commented Dec 13, 2022

Hi @petrkoutnycz. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

@ghost ghost removed the needs-team-attention This issue needs attention from Azure service team or SDK team label Dec 13, 2022
@ghost
Copy link

ghost commented Feb 13, 2023

Hi kristinannabel, only the original author of the issue can ask that it be unresolved. Please open a new issue with your scenario and details if you would like to discuss this topic with the team.

1 similar comment
@ghost
Copy link

ghost commented Feb 13, 2023

Hi kristinannabel, only the original author of the issue can ask that it be unresolved. Please open a new issue with your scenario and details if you would like to discuss this topic with the team.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Functions issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

5 participants