Blueprint 3.0.6
Richard Crowley
issues closed since 3.0.5. Many of those commits are
behind-the-scenes, refactoring to lay the groundwork for a more
maintainable future. That doesn't mean there aren't some cool
features, though.
First up is the much improved support for the various ways people use
sudo to gain temporary root access and root shells through -i. I
expect most if not all strange GitError exceptions talking about lack
of permissions to be a thing of the past.
Next, ever-smarter defaults for ignoring files to keep your blueprints
free of noise: Blueprint won't bother you about things you didn't
change in /etc/pam.d, about Debian's CD-ROM, or backup files.
blueprint-create, blueprint-show, and blueprint-apply all now support
the --relaxed option that generates code without strict version
numbers so any version of a package will suffice. This is
particularly helpful (and recommended) for users that don't mirror
their distro's package archive.
And finally: service resources. Now Blueprint will track down
services that are running plus the files and packages that influence
them. These translate directly to service resources in the generated
Puppet and Chef code. In the generated shell code, changes to any
file or package will cause the corresponding services to be restarted
at the end. Now you can use blueprints all by themselves to deploy
your environment and application to production.
As always, Matt and I are listening for issues and feature requests,
and would love to know how you're using Blueprint.
Richard
Richard Crowley
Source: https://github.com/devstructure/blueprint
Changes: https://github.com/devstructure/blueprint/compare/v3.0.5...v3.0.6