Martin Chvíla
Martin Chvíla
Currently, as I understand the flow from the testing: - the orchestrator triggers _Github workflow_ with _terraform plan_ in every _project_ that is adapted in any commits in the PR...
When the organisation policy already exists and I am using the API call again to update it, it fails on SQL error API command used (both first time and update):...
Every "Job status" comment contains a link. I would expect this link to redirect to Github Action run, but instead it redirects to URL of the PR itself (which is...
Using v 0.4.6. For project that use Terragrunt, during digger plan, Digger CLI is outputting full plan JSON (as if I would use terraform show -json plan.tf - https://developer.hashicorp.com/terraform/internals/json-format )....
Current flow (simplified): On commit, digger orchestrator executes github workflows for each affected project. Inside that workflow, it checks if the actor has allowed the action (apply, plan) in policy....
v0.3.25 PR is opened with change in a Project. Actor who is not allowed to apply runs "digger apply" Workflow starts, inside it checks the policy and finishes with: ```...
We have Github repo setup to delete every feature branch on merge to main. (Settings, General)  Digger is processing an github event pull_request.closed after which I assume it runs...
Message after policy violation is wrong, variables command and user are switched: User digger apply is not allowed to perform action: chvima. Check your policies ❌
v0.3.21 using orchestrator, self hosted digger, self hosted runners Exception: ``` Using GitHub. GitHub context parsed successfully panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation...