Garison Draper

This sets the tags on every run, just like with cloudformation.

The CI failure looks like an IAM role issue of some sort, or AWS issue. Let me know if I'm wrong with that assumption and need to revisit this PR.

@phobologic - I went over this with @troyready this morning and came up with a concern with the path I went down to solve this. I want to take another...

@phobologic - TLK was shorthand for "Top Level Keyword". I have amended my PR to include a new TLK for "bucket_tags" that falls back to the tags behavior if not...

That's how I was leaning... I think it's a good idea to hold off on #496 until later, but perhaps put in a deprecation warning instead. This way, people can...

@phobologic, Any feedback on this idea? I'm probably going to try to take a stab at it this weekend (if I can find the time.) A feature like this would...

I agree Eric re: your namespace comment and have had that thought in the past when thinking about this. We would need some sort of "xref" like ability at the...

@ekenstam - My script was never finished as I ended up not needing the ability in the job I was working at the time, but you are welcome to see...

Yeah - I have been manually adding in the stacker_namespace tag in my configs to get it back in there... I so I guess I agree with you since I...

@phobologic - Fourth potential feature needing to be included, updating tags on subsequent runs... as in, I have hundreds of S3 buckets already deployed by this function (the aws_lambda hook...