Apache2 should not restart unnecessarily after a deploy

[nickmarden]

The current implementation of the Apache2 webserver driver always restarts at the end of a deployment. This restart can be necessary when the Apache2 configuration has changed so much that modules must be loaded or reloaded, for example, but it is not generally necessary as a deploy typically will only result in the underlying app(s) having been updated without change to the apache configuration.

As an opsworks_ruby user, I would like the default behavior for deploys to be to reload the apache2/httpd service rather than restart-ing it, so that the server will continue to serve requests throughout the deployment Chef run.

Implementation expectations:

• Any action (e.g. installing a module) that would cause the Apache2 configuration to become invalid and require a restart, will still cause Apache2 to restart at the end of the Chef run
• Otherwise, Apache2 will only reload after a deploy

Bonus points:

• Implement the same for nginx