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

Accept the token credential and fully qualified namespace as separate arguments instead of in a connection string #658

Merged
merged 2 commits into from Oct 28, 2022

Conversation

danielmarbach
Copy link
Contributor

@danielmarbach danielmarbach commented Oct 28, 2022

@danielmarbach danielmarbach changed the title Make the token credential and the fullyQualifiedNamespace a dedicated connection setting instead of abusing the connection string. Make the token credential and the fullyQualifiedNamespace a dedicated connection setting instead of misusing the connection string. Oct 28, 2022
danielmarbach and others added 2 commits October 28, 2022 22:15
… connection setting instead of abusing the connection string.
Co-authored-by: Brandon Ording <bording@gmail.com>
@danielmarbach danielmarbach enabled auto-merge (squash) October 28, 2022 20:16
@danielmarbach danielmarbach merged commit ae84af1 into master Oct 28, 2022
@danielmarbach danielmarbach deleted the token-credential branch October 28, 2022 20:33
danielmarbach added a commit that referenced this pull request Nov 2, 2022
… connection setting instead of misusing the connection string. (#658)

* Make the token credential and the fullyQualifiedNamespace a dedicated connection setting instead of abusing the connection string.

* Update src/Transport/AzureServiceBusTransportSettingsExtensions.cs

Co-authored-by: Brandon Ording <bording@gmail.com>

Co-authored-by: Brandon Ording <bording@gmail.com>
# Conflicts:
#	src/Transport/AzureServiceBusTransport.cs
@danielmarbach danielmarbach added this to the 3.0.0-rc.3 milestone Nov 11, 2022
@danielmarbach danielmarbach changed the title Make the token credential and the fullyQualifiedNamespace a dedicated connection setting instead of misusing the connection string. Expose the token credential and the fully qualified namespace as a dedicated connection setting instead of the connection string Nov 17, 2022
@adamralph adamralph changed the title Expose the token credential and the fully qualified namespace as a dedicated connection setting instead of the connection string Expose the token credential and the fully qualified namespace as a dedicated connection setting instead of the connection string Nov 17, 2022
@danielmarbach danielmarbach changed the title Expose the token credential and the fully qualified namespace as a dedicated connection setting instead of the connection string Accept the token credential and fully qualified namespace as separate arguments instead of in a connection string Nov 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When using TokenCredential validate if connection string only contains the fully qualified namespace
2 participants