Probably my lack of understanding of how vagrant fits and works. But you wouldn't use vagrant to manage a production server, so there's an inevitable difference there.
See, you wouldn't use vagrant to manage a dev server either. Rather, the idea is that, in dev, you use vagrant to provision a VM (or multiple VMs; you can replicate your whole stack with multiple web servers, database clusters, load balancers, etc.) which is as close to your production environment as possible. Then you manage this dev environment the exact same way you manage your production environment - with chef or puppet.
Vagrant is taking the role of Amazon's EC2 control panel or the order form on your dedicated server providers website. And none of those manage the server; that's chef or puppets job. (Although it does have great integration with chef and puppet.)
See, you wouldn't use vagrant to manage a dev server either. Rather, the idea is that, in dev, you use vagrant to provision a VM (or multiple VMs; you can replicate your whole stack with multiple web servers, database clusters, load balancers, etc.) which is as close to your production environment as possible. Then you manage this dev environment the exact same way you manage your production environment - with chef or puppet.
Vagrant is taking the role of Amazon's EC2 control panel or the order form on your dedicated server providers website. And none of those manage the server; that's chef or puppets job. (Although it does have great integration with chef and puppet.)