Feat(cv_deploy): cv_static_config_manifest to support multiple sites #6562
Description
Enhancement summary
In the current state, cv_deploy cv_static_config_manifest only allows for a single manifest file for all sites. If you have multiple sites with separate manifest files per site, cv_deploy will rewrite the last container with the new one and remove configlets from the previous Static Configuration Studio container.
Which component of AVD is impacted
cv_deploy
Use case example
Customer has multiple sites managed with AVD and separate cv_static_config_manifest per site. They wish to break out a separate cv_static_config_manifest container per site.
Describe the solution you would like
Customer has multiple sites managed with AVD and separate cv_static_config_manifest per site. They wish to break out a separate cv_static_config_manifest container per site.
Desired Static Configuration Studio container hierarchy:
Describe alternatives you have considered
Today the customer must use a single cv_static_config_manifest for all sites with a single Static Configuration Studio container.
Static Configuration
----- AVD Generated Configlets
----- Site 1 Static Configlets (tag_query: "Site1:")
----- Site 2 Static Configlets (tag_query: "Site2:")
Additional context
No response
Contributing Guide
- I agree to follow this project Code of Conduct