Michael Barrett

So I've been thinking about this - a couple of thoughts: The easiest way to get this in is to likely make it just part of the stacks config directly...

@xiaket It's been a while, but I think there is a reason why that regex matches - just can't remember what it is. I think a bigger issue has always...

btw, one thing I've been working on for some time now is removing the use of the regex altogether and using an actual parser... pyparsing to be specific. I think...

What about if, before stacker will do a build/destroy, it first checks the current status of each of the stacks in it's plan - if any of them are in...

I think automatically providing some tags could be a good idea - probably at least `stacker_namespace`? It's always bothered me that https://github.com/remind101/stacker/blob/ecd8933d715da8ede5b0d6e6d1e98bd827ff6b43/stacker/context.py#L97 removed the `stacker_namespace` tag automatically if you provided...

Definitely a different issue - just wanted to make sure we don't make the same "mistake" here :)

That sounds fine to me - I don't think anything would be broken by adding tags. The bigger question is what it's going to do for performance - I imagine...

Yeah, I think the only tag we would probably add by default is `stacker_namespace` - and we can just skip adding that if it is manually defined already. Thanks for...

Thanks @xiaket - I can see how that would cause problems. Have you tried escaping the variables in the userdata? I'm actually not sure if that would help or not...

@discobean What version of stacker are you using? Can you share the relevant parts of the config & blueprint when it breaks? Thanks!