AaronC03/13/2023, 5:29 PM
feature. I had this working previously but since I upgraded to the latest release it seems like no matter what I do the auto-plan is never triggered. I can see the
file is being parsed correctly on each merge requests yet I constantly see the log message
I am sure I am missing something trivial here but the pathing is correct etc, so I don’t really know what else I should be toggling.
0 projects are to be planned based on their when_modified config
Any help would be appreciated.
version: 3 automerge: true delete_source_branch_on_merge: true parallel_plan: true parallel_apply: true projects: - name: some-module dir: some/nested/path/some-module branch: /main/ workflow: terragrunt delete_source_branch_on_merge: true repo_locking: true autoplan: when_modified: [ "../../../../inputs/base/test/data.yaml", ] enabled: true apply_requirements: [mergeable, approved, undiverged] import_requirements: [mergeable, approved, undiverged]
PePe Amengual03/14/2023, 3:09 AM
AaronC03/14/2023, 1:19 PM
with some extra debugging around the
function for Gitlab. It seems that it’s actually getting an empty slice of changes from Gitlab when it queries it immediately after the web-hook is triggered, all the other fields are in place but
is empty. Which makes no sense because when I hit the exact same API call I see a list of changes. Just to prove this out in a brute force method I put a sleep inside the function to ensure Gitlab had fully updated everything before we ask for the changes, it has worked every single time after about 2 dozen tests.
PePe Amengual03/14/2023, 4:20 PM
AaronC03/14/2023, 5:02 PM
PePe Amengual03/14/2023, 5:27 PM
AaronC03/14/2023, 5:28 PM
PePe Amengual03/14/2023, 5:29 PM