Subject: [chef] Chef for application config / deployments

Its more of just a marketing thing since they are selling all their products as a complete automation stack and have always billed habitat as application automation they just renamed chef to chef infra for marketing purposes. They wouldn't remove any functionality you currently use for installing applications because its core functionality to chef infra. They just wanted to have a way to label the different parts of their stack I wouldn't worry about it.