Skip to content

chore: revert - Default deployment mode to "standard" instead of "workshop"#221

Draft
Pavan-Microsoft wants to merge 8 commits intodevfrom
psl-pk-revertworkshop
Draft

chore: revert - Default deployment mode to "standard" instead of "workshop"#221
Pavan-Microsoft wants to merge 8 commits intodevfrom
psl-pk-revertworkshop

Conversation

@Pavan-Microsoft
Copy link
Collaborator

Purpose

This pull request updates both the deployment configuration and the agent creation script to simplify deployment modes, improve tagging, and streamline agent instructions. The changes remove the distinction between "workshop" and "standard" deployments in several places, default deployments to "standard" mode, and improve resource tagging in the infrastructure code.

Deployment configuration and resource tagging:

  • Default deployment mode is now "standard" instead of "workshop", and the documentation and parameters have been updated accordingly. The environment variable and parameter defaults for isWorkshop are now set to false. [1] [2] [3] [4]
  • Resource tagging is improved: tags are now correctly applied to managed identities and all Azure resources, using a union of resource group tags, deployment-specific tags, and user-supplied tags. The tags parameter is now enabled and used throughout the Bicep and generated ARM templates. [1] [2] [3] [4] [5] [6] [7] [8]
  • The default values for backendRuntimeStack and usecase parameters have been removed, requiring explicit values during deployment. [1] [2] [3]

Agent creation script simplification:

  • The agent creation script (01_create_agents.py) is refactored to remove all logic and instructions related to the "workshop" deployment mode, consolidating to a single set of agent instructions. The script no longer accepts or checks for is_workshop, and the tools and instructions are simplified. [1] [2] [3] [4]

Documentation update:

  • The deployment guide is updated to clarify that the default mode is now "standard", and users are directed to a separate workshop guide if they want to run the workshop scenario.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

- Deleted 02_upload_documents.py and its requirements as they are no longer needed.
- Removed run_search_index_scripts.sh and related SQL item scripts to streamline the deployment process.
- Updated run_workshop_data_setup.sh to reflect changes in environment variable handling and removed unnecessary parameters.
- Cleaned up create_sql_items.py by removing unused imports and functions.
- Updated documentation to clarify workshop mode setup and deployment instructions.
- Added IS_WORKSHOP and AZURE_ENV_DEPLOY_APP flags to .env.sample for better configuration management.
@github-actions
Copy link

github-actions bot commented Feb 16, 2026

Unit Test Results

482 tests  +18   482 ✅ +30   7s ⏱️ ±0s
  1 suites ± 0     0 💤 ± 0 
  1 files   ± 0     0 ❌  - 12 

Results for commit 8baacdc. ± Comparison against base commit 83f0b3c.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Feb 16, 2026

.NET Unit Test Results

201 tests  ±0   201 ✅ ±0   2s ⏱️ +2s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 647ed04. ± Comparison against base commit 83f0b3c.

♻️ This comment has been updated with latest results.

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