Olaf Conijn

I think this would be a great addition. I would, however, prefer to keep the syntax compatible with CloudFormation [see here](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-conditions.html#intrinsic-function-reference-conditions-if). this means that your 1st example would work, but...

nice! agree that functions must be better composable. i had not run into this before, but will look into fixing this for sure. one thing: `!Cmd cat file.json` -> not...

ah, ok. !ReadFile also doesn't allow to me used to produce the template of a !Sub (for now)

thanks for sharing! I have not tried to run org-formation in me-south-1 yet. I will give this a try tomorrow. what might remediate the issue is to run the init...

I just tested the following in `me-south-1` ``` ofn init org.yml

hi, before we continue, if you are using a beta would be good to give this a try with the most recent release instead. there has been a similar bug...

so if i understand correctly, something like this ``` yaml FeatureDev: Type: include DependsOn: FeatureCore Path: ./feature-tasks.yml Parameters: resourcePrefix: !Sub "${resourcePrefix}-dev" Tags: [DEV] FeatureProd: Type: include DependsOn: FeatureCore Path: ./FeatureCore-tasks.yml...

I would expect the behaviour that is described in this issue: if you run 5 tasks concurrently, you might get up to 5 failures with `--failed-tasks-tolerance 1`. The reason is...

I've been going back and forth on how to implement this, I think I really like the suggestion put forward in the PR. I think how most people would likely...

great, thanks!