S
Satisfied Lark
Description:
IACM Workspace Templates currently lack granular override capabilities for key configuration parameters, particularly Git connection details (such as repository URL, branch, and folder/base path). Because these fields cannot be individually overridden during workspace creation or instantiation, a single template is artificially restricted to a single repository, branch, or directory structure.
We request the ability to expose and override individual configuration fields—specifically Git settings (repository, branch, path/folder), environment variables, and execution parameters—when instantiating a workspace from a template. This would allow a single, standardized template definition to be reused dynamically across multiple repositories, environments, and team configurations.
Business Impact:
  1. Scalability & Reusability: Unlocks true template reusability across enterprise teams, drastically reducing the total number of duplicate templates platform engineers must create and maintain.
  2. Standardization with Flexibility: Allows central platform teams to enforce workspace governance and pipeline baselines while giving application teams the flexibility to point to their specific repos, branches, and code paths.
  3. Lower Maintenance Overhead: Simplifies platform operations by allowing global configuration updates to be managed in one core template rather than spread across dozens of single-use template variants.