Added initial version of the blueprint-cfn command #126
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So, we use lots of cloudformation. Amazon's cfn-init scripts kinda suck, since they don't act like blueprint does in all cases -- especially when you want to use a blueprint to update a box. So, we built this little tool to allow someone to easily pull the metadata section of the LaunchConfiguration and execute it with normal blueprint. Right now, we kick these updates semi-manually, with fabric. In the near future, we'd very much like to have a daemon that subscribes to the SNS channel monitoring changes to the stack (or poll, if desired.)
Boto is required to run blueprint-cfn, but we didn't add it as a requirement to the blueprint project -- we just print out a message instructing the user to install it.