Add Durable triggers to TriggersWithoutStorage #509
Merged
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
We plan to release public support for non-Azure Storage backends for Durable Functions. In order for the VS build SDK to fully support this, we need to exclude Durable triggers from the list of triggers requiring `AzureWebJobsStorage`. Note that we already made the same change for the Functions Core Tools: Azure/azure-functions-core-tools#2409
|
@divyagandhisethi - once Azure/azure-functions-host#7327 is rolled out - please send a PR to exclude TimerTrigger as well. |
pragnagopa
approved these changes
May 10, 2021
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.
We plan to release public support for non-Azure Storage backends for Durable Functions. In order for the VS build SDK to fully support this, we need to exclude Durable triggers from the list of triggers requiring
AzureWebJobsStorage.Note that we already made the same change for the Functions Core Tools: Azure/azure-functions-core-tools#2409