Skip to content

chore: remove unused deployment scripts and update AVM post-deployment guide#2184

Open
Abdul-Microsoft wants to merge 1 commit intoAzure-Samples:devfrom
Abdul-Microsoft:chore/avm-post-deployment-script-update
Open

chore: remove unused deployment scripts and update AVM post-deployment guide#2184
Abdul-Microsoft wants to merge 1 commit intoAzure-Samples:devfrom
Abdul-Microsoft:chore/avm-post-deployment-script-update

Conversation

@Abdul-Microsoft
Copy link
Copy Markdown
Contributor

Purpose

  • This pull request updates the post-deployment process for setting up PostgreSQL and related documentation. The main focus is on simplifying and consolidating the table creation process into a single post-deployment script, and updating the documentation to reflect these changes. Several scripts used for credential management and table creation have been removed, and the documentation now emphasizes running a unified setup script after deployment.

Documentation updates:

  • Updated the post-deployment guide (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]
  • Revised the PostgreSQL integration documentation (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:

  • Removed the azure_credential_utils.py script, which previously handled Azure credential acquisition for both sync and async environments.
  • Deleted the create_postgres_tables.py script, which handled PostgreSQL table and index creation using Azure credentials.
  • Removed the run_create_table_script.sh Bash script that managed firewall rules, requirements installation, and table creation script execution.

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install
  • Test the code

What to Check

Verify that the following are valid

  • ...

Other Information

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant