Eric Holmes

This is definitely a bug. I’ll dig in when I have time (or happy to review if someone sends a PR). One easy way around this would be to create...

I was thinking a bit about this recently. What if we just allowed people to create their stacker bucket, with stacker? I was thinking of supporting something like this in...

So, we (internally) actually switched over to a method similar to what I outlined above, without any changes to stacker. Our stacker config now has a stack that creates a...

On a similar note, at times I've felt it would be easier to describe everything in Python, rather than YAML. That would easily allow for transformations, conditions, and math using...

@jamietsao by the looks of it, somehow stacker is using an old version of boto. Can you post what version of boto3/botocore is getting used? This error shouldn't show up...

I think the diff exception is probably a legitimate bug, but glad to know that upgrading boto3 fixed the original problem.

I've been thinking a bit about this. I think you could just subclass `stacker.blueprints.base.Blueprint` and override the [`render_template`](https://github.com/remind101/stacker/blob/master/stacker/blueprints/base.py#L455) method to just return some raw CloudFormation json. Atleast as a quick...

I meant that if you have stacker configured with a namespace, but you have existing stacks in CloudFormation that don't match that namespace, you can't really import those stacks into...

I've run into this problem a few times as well in the past. Although vars from the environment file look similar to lookups, evaluating happens more like rendering a template....

@syphon7 lookups get processed at runtime, as needed, whereas env files are processed like a template as one of the first steps of a stacker build/destroy. The `stacker.yaml` file gets...