fix: local deployment setup#2182
Merged
Avijit-Microsoft merged 5 commits intoAzure-Samples:devfrom Apr 24, 2026
Merged
Conversation
Avijit-Microsoft
approved these changes
Apr 24, 2026
This file contains hidden or 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.
Purpose
This pull request updates the local development setup documentation and Azure configuration to simplify Python dependency management and clarify instructions for developers. The main focus is on consolidating dependency installation for backend and batch functions, and making minor adjustments to configuration requirements.
Documentation improvements:
docs/LocalDevelopmentSetup.mdto clarify that both backend and batch functions share dependencies managed by the rootpyproject.toml, eliminating the need for separate installation steps for the batch function. Also, added a note to make this explicit.Configuration update:
bicepversion requirement from theazure.yamlconfiguration, potentially allowing for greater flexibility in tool versions.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information