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

Fix breaking change when Active Directory ID is used as host in WASB #32560

Merged
merged 3 commits into from
Jul 12, 2023

Conversation

ephraimbuddy
Copy link
Contributor

A recent change: 46ee1c2,
to build account url if not provided broke backward compatibility in Wasb hook by assuming that
host is always provided as a fully qualified url. Previously, we generate the account url
as the last resort to getting the connection.

This change restores the previous behaviour of generating a URL if the host was provided with an ID
instead of a URL

A recent change: apache@46ee1c2,
to build account url if not provided broke backward compatibility in Wasb hook by assuming that
host is always provided as a fully qualified url. Previously, we generate the account url
as the last resort to getting the connection.

This change restores the previous behaviour of generating a URL if the host was provided with an ID
instead of a URL
@ephraimbuddy ephraimbuddy merged commit fcbf159 into apache:main Jul 12, 2023
@ephraimbuddy ephraimbuddy deleted the fix-azure branch July 12, 2023 16:49
Copy link
Member

@pankajkoti pankajkoti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would we need to yank the earlier release of the provider?

@ephraimbuddy
Copy link
Contributor Author

Would we need to yank the earlier release of the provider?

I think quickly releasing a patch will suffix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants