Igor Zalutski
Igor Zalutski
project autodetection, how to detect the dependencies between NOT detecting the. common directory inside and also being able to figure out that there are dependencies and are common > also...
Understanding of how the orchestrator and the digger cli communicates Additionaly great to have with GH hosted runners + internally hosted orchestrator - way to understand traffic / call flow...
Our dependencies / include patterns implementation only conciders "static" graph based on folder structure. This leads to following problems: - downstream dependencies triggering when there is no actual change affecting...
For N projects, we'd want 3N + 3 checks: - N apply checks (one per project) - 1 aggreagate apply check - N plan checks (one per project) - 1...
Lots of comments create noise. This is partially addressed in #1136 but it'd be even better if we relied on status checks for everything that does not contain valuable information....
Currently supporting [sops](https://github.com/getsops/sops) would require granting the orchestrator backend privileges to decrypt them, because it checks out the repo prior to starting the jobs. This is not ideal from security...
Currently Digger orchestrator checks out the repo first in order to parse digger.yml and determine the impacted projects. This approach is problematic for 2 reasons: 1. The orchestrator has to...
Hi Zapier engineers, you might have heard of the recent license changes by Hashicorp Please consider joining our pledge to keep terraform open: [The OpenTF Manifesto](https://opentf.org) - - - Igor,...
Currently rendering of the initial comment by the backend and rendering of updates share similar pieces of logic (table, statuses etc) We'd want it in shared libs ideally Backend: pr_comments.go...