fix: Post-Deployment Script for Managing Bicep Outputs in .env File and Update Conversation flow based on template selection #1567
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
Post-Deployment Script for Managing Bicep Outputs in .env File and Update Conversation flow based on template selection
User Story 11717: [Bicep] | [CWYD] - Post-Deployment Script for Managing Bicep Outputs in .env File
Bug 11703: [SmokeTesting] - CWYD - Even if we select Conversation flow as "BYOD" while deploying cwyd, once deployed on admin page under configuration it's set to "Cutom" by default.
Does this introduce a breaking change?
How to Test
What to Check
Outputs exceeding the 64-item limit are processed and The script formats the consolidated output into .env key-value pairs.
If we select "byod" as conversaion_flow, it should come as "byod" only once deployed, on admin page.