Ben Carter

@ZIJ We have run into the dependency one. I noticed in the code it does look like it is attempting to use ExecutionOrderGroups now. Is part of this been implemented?

This is a really key feature for us as well

I did notice this yesterday for the GitHub CI. It looks like it checks IsMergeable so if you have approvals or status checks set up it will not allow they...

Would really like to see this feature to reduce the time of runner and reduce external dependencies coming in for more regulated environments.

@motatoes retested this today. The cause was the dispatch with no-backend = true. If you change it to PR workflow and no dispatch, it does work fine, as you pointed...

The current workaround is adding the AWS_REGION to the environment variable for the workflow so it is picked up by the credential call See below for an example: ```yaml jobs:...

One thing I am testing is this in the digger.yml to see if it fills the need without having to change the workflow file. Because if I update the workflow...

I finally got around to testing this today and using this technique to set the region did not work: ```yaml workflows: default: env_vars: state: - name: AWS_REGION value: "us-west-2" commands:...

I think I found the problem, when examining an environment with the workflow vars set when I looked at initialize digger config: I see this: ```yaml Run diggerhq/[email protected] with: setup-terraform:...

I would like to vote this up, I encountered this today as well.