Progress Chef Reviews & Product Details

Automation has never been so easy to do, whether it is a server or other software-related workload; the progressive chef is handy has always been a forte. My team started using progressive chef before puppet or even ansible, and it's still everyone's favorite Review collected by and hosted on G2.com.

Not everyone had it easy with how to use it from the start, but after a while, everyone was alright. Create more developer advocates and communities around the product. Review collected by and hosted on G2.com.

I like their support and Chef meetings plus Chef is easy to manage and implement when the company has great support, it does adds to the value of the product. Review collected by and hosted on G2.com.

Nothing, it's a great product, and it is very well supported. Review collected by and hosted on G2.com.

We have used Chef for 10+ years as our configuration management tool. The Chef Infra infrastructure has been robust and provided a stable platform for us to develop against. The out of box functionality solves many of our use cases and the Chef DSL provides enough extensibility that we can create functionality for our specific use cases. Review collected by and hosted on G2.com.

My main dislike about Chef is the care and feeding required to perform a chef-client update. Usually, taking a chef-client upgrade takes us at least a month to work through rolling it out across our organization. We have chef-client running daemonized in many environments, and the upgrade process stops the automatic runs for about a 24-hour period, which means we could have server drift during this window. This means we have to be picky about which version of chef-client we run, and usually wait until a new major version is released, upgrade, and then sit on that version until EOL. Ideally, we'd love to keep that current as much as possible. Review collected by and hosted on G2.com.

Progress Chef allows our developers to have more control over their web application infrastructure, thereby allowing the developers to roll out web applications and services more quickly. Review collected by and hosted on G2.com.

- Figuring out the syntax required in Ruby to implement a given resource update is sometimes difficult.

- It's not easy to pass status information from powershell scripts back to Chef/Ruby.

- It's not real clear what Progress Chef is responsible for vs the Chef community. Review collected by and hosted on G2.com.

Chef is a great product, and it solves many of the problems we have with compliance and policy enforcement. We have reasonably good support from our success team. Review collected by and hosted on G2.com.

Development on the product seems hit or miss, sometimes rushed and not always well documented. Sometimes our customer success resources aren't sure how to solve our problems. It seems evident that something has happened internally to Progress/Chef, which is impacting their ability to develop and release stable products. This is a little panic-inducing for a company using Chef across an install base of nearly 70,000 servers. Review collected by and hosted on G2.com.

I started using chef products over the last 8 years, and I became an expert in chef software running kitchens, chef knife cli, compliance, inspect, easy to integrate API's with other applications, pipeline, ruby language easy to use and get familiar quickly using chef error handling messages. Chef configuration management and deployment application. Review collected by and hosted on G2.com.

Nothing at this point and no comments about any dislike of the product. Review collected by and hosted on G2.com.

The Progress Chef team is responsive and reachable. They react to concerns and are always ready to help. The tools are best-of-breed and are constantly being improved. Review collected by and hosted on G2.com.

Documentation of new features can often be a bit sparse, and discovering said new changes can be a bit difficult. Documentation also varies in detail level and scope. Review collected by and hosted on G2.com.

Formerly known as CHEF, it is used to manage all the slave systems, so we don't have to manually log in to each of the slave nodes or machines to be able to install software systems. I used it when I was working in one of the previous product organization. We used CHEF to install multiple dependencies on the system by defining a cookbook and recipe. So basically we can define a set of tasks which has to be executed on the system and CHEF automatically logs in to the system and does the software install, package install or maybe change the configuration. In the big data world, suppose a node is required to have the software needed before it can operate. we just can run chef-client and it does everything automatically. This is an amazing tool and works fast without any hassles. Review collected by and hosted on G2.com.

Since it is built on top of ruby, sometimes it's hard to figure out what has caused the error. There have been instances where the chef-client has failed, and it was pointed to an error, and late we got to know that it is related to ruby installation. sometimes, the chef errors are hard to debug. There is no intelligent troubleshoot mechanism and does not suggest user where to look for exact errors and fixes. Review collected by and hosted on G2.com.

Everything is as code, so it's flexible and easy to reuse code. There are many pre-made cookbooks available on the Chef Supermarket to deploy a wide variety of software. Review collected by and hosted on G2.com.

- Test Kitchen and Chef InSpec are too rigid and prevent testing more advanced scenarios, e.g., upgrading a service from version A to B.

- Since there's no notion of state, it is hard to track resources that need to be deleted.

- The attributes precedence logic is way too complicated. Review collected by and hosted on G2.com.

Centralizing our configuration management for all of our managed nodes through cookbooks for all of our environments. Visibility into the cached cookbooks and ability to test locally. Review collected by and hosted on G2.com.

Repeatability is tricky with Chef's two-pass model. Troubleshooting is challenging once the Chef codebase grows significantly. The attributes precedence evaluation is funky. Review collected by and hosted on G2.com.