chore: remove unused deployment scripts and update AVM post-deployment guide#2184
Open
Abdul-Microsoft wants to merge 1 commit intoAzure-Samples:devfrom
Open
Conversation
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
Documentation updates:
AVMPostDeploymentGuide.md) to instruct users to run a single post-deployment setup script for configuring the Function App client key and creating PostgreSQL tables, streamlining the previous multi-step process. Steps for authentication and accessing the admin/chat apps have been renumbered accordingly. [1] [2]postgreSQL.md) to clarify that table creation is handled by a single post-deployment script, replacing references to automated table creation during infrastructure deployment. The benefits section now highlights the simplified, script-based setup. [1] [2]Script and code cleanup:
azure_credential_utils.pyscript, which previously handled Azure credential acquisition for both sync and async environments.create_postgres_tables.pyscript, which handled PostgreSQL table and index creation using Azure credentials.run_create_table_script.shBash script that managed firewall rules, requirements installation, and table creation script execution.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information