Use rpcBaseUrl in durable operations when possible #1098
+18
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue describing the changes in this PR
When experimenting with Azure/azure-functions-durable-powershell#73, I found that if a user does not explicitly call Import-Module on the external SDK, functions that are exposed in the external Durable SDK are not used, and instead the definitions loaded in the bundled module are used.
This change imports the fix from Azure/azure-functions-durable-powershell#66 into the bundled module, with additional checks to prevent breaking backwards compatibility.
Pull request checklist
release_notes.md