S
Satisfied Lark
Description:
Infrastructure as Code Management (IACM) workspaces currently trigger auto-execution pipelines based on changes within the defined base_path. However, modern IaC architecture frequently relies on external, shared dependencies located outside the primary workspace directory—such as centralized module templates, global variables, shared policy definitions, or cross-environment YAML configurations.
We request the ability to specify a list of "Watched Directories" or "Additional Trigger Paths" for an IACM workspace alongside the base_path. When a commit modifies files within any of these specified paths, the workspace should automatically detect the change and trigger the execution pipeline (e.g., plan/apply).
Business Impact:
  1. Risk Mitigation: Eliminates the risk of configuration drift or undetected failures caused by unapplied changes to shared configurations and modules.
  2. Operational Efficiency: Removes the need for manual, error-prone pipeline triggers or complex custom webhook workarounds whenever common modules or shared configs are updated.
  3. Scalability: Enables standardized, DRY (Don't Repeat Yourself) infrastructure repository layouts across enterprise teams without sacrificing automated continuous integration and delivery.