stacker import capability to create blueprints from existing cloudformation

So, I wanted to open this up to start a discussion about something I kind of want to work on to help with the massive existing JSON CFN problem we have at Sturdy. Recently @troyready and I had a quick conversation in passing about the problem we will eventually have: getting the thousands of exisiting deployed CFM stacks from our older clients into stacker blueprints so we could potentially use them elsewhere/redeploy. If we had a way to import a deployed stack into a blueprint, that would help... even if it's a blueprint without any defined variables. At least we would have a starting point.

Troy mentioned this: https://github.com/cloudtools/troposphere/blob/master/scripts/cfn2py

I'm wondering what you guys think about the idea. I'm imagining something like `stacker import ` would build a blueprint and populate the troposphere portion of the blueprint by using the native cfn2py functionality. Then I would have a real blueprint that could be a part of my stacker yaml config.

What does everyone think?

Inizia leggendo lo script cfn2py di troposphere collegato e valutando come il suo output potrebbe diventare un blueprint di stacker. Poi analizza il flusso proposto `stacker import ` e come accederebbe a uno stack esistente già distribuito. Il lavoro è completato quando si è concordato l’ambito dell’importazione e si è prodotto un blueprint utilizzabile, incluso uno senza variabili definite.

Scritto dal modello di indicizzazione a partire dal testo della issue.