Andrew Glenn

@TejjeT The only remaining question I have is around project root. ``` ❯ tree . -a . ├── .taskcat.yml ├── testA │   └── .taskcat.yml ├── testB │   └── .taskcat.yml ├──...

This is a bit more complicated than meets the eye, namely due to the multiple permutations of bucket naming formats we have. The format you're using is "legacy", (ex: `s3_regional_buckets`...

Thought: May need to account for situations where AMI wildcards are not consistent across partitions.

Law of unintended consequences. I'll look at this next week.

Is this a blocker, or nice-to-have? That aside, this appears as a breaking change at first glance, since we assume `key:value` under parameters... Will we introduce backwards compatibility ? Assuming...

> It's not a breaking change. Without additional logic, it is. Current test definitions expect.. ``` parameters: key: value ``` Not ``` parameters: region_name: key:value ``` We'll need to add...

> > since we assume key:value under parameters > > parameters can be any type except dict at present (cfn doesn't accept dict). All this will introduce is that IF...

@jaymccon I'm good with this. It just means a few more calls to the template_params stuff. Would it make sense to craft a list of parameter `sources`, like what's done...

Just to circle back - I'm running into a situation where this would mitigate pain. Any questions on the value-add I had are now gone.

@avattathil what's your ideal use-case? It's not clear from the proposed config. Caveat, I need more :coffee: