(Take 2) Permission denied when calling step function within step function in standard workflow using sync pattern

[terrysiu-pm]

Description

This is a continuation of #59 which is closed and locked due to inactivity.

Same issue still exists in 4.2.0 of this module. Per the original issue, the fix should just be introducing a conditional assignment using var.type and assign states:StartSyncExecution if the type is EXPRESS, otherwise, assign states.StartExecution.

As a temporary workaround for STANDARD workflows, an additional policy can be created (and attached) which grants additional states:StartExecution for the child workflow.

If your request is for a new feature, please use the Feature request template.

• ✋ I have searched the open/closed issues and my issue is not listed.

⚠️ Note

Before you submit an issue, please perform the following first:

1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
2. Re-initialize the project root to pull down modules: terraform init
3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

• Module version [Required]: 4.2.0

• Terraform version: 1.8

• Provider version(s): 5.63.0

Reproduction Code [Required]

See #59

Steps to reproduce the behavior:

See #59

Expected behavior

See #59

Actual behavior

See #59