2019-08-23 14:22:47 -07:00
|
|
|
---
|
2023-06-02 21:41:36 -07:00
|
|
|
title_tag: "Pulumi vs. Chef, Puppet, Ansible, and Salt"
|
2022-12-13 15:19:37 -08:00
|
|
|
meta_desc: Learn about the major differences between Pulumi and configuration management tools like Chef, Puppet, Ansible, Salt, and more.
|
2023-05-15 15:25:28 -07:00
|
|
|
title: Chef & Puppet
|
|
|
|
|
h1: Chef, Puppet, Ansible, & Salt vs Pulumi
|
2023-06-08 16:15:52 -07:00
|
|
|
meta_image: /images/docs/meta-images/docs-meta.png
|
2019-08-23 14:22:47 -07:00
|
|
|
menu:
|
2023-05-15 15:25:28 -07:00
|
|
|
concepts:
|
2019-08-23 14:22:47 -07:00
|
|
|
parent: vs
|
2019-09-10 08:04:15 -07:00
|
|
|
weight: 7
|
2021-09-14 07:48:43 -07:00
|
|
|
aliases:
|
|
|
|
|
- /docs/reference/vs/chef_puppet_etc/
|
|
|
|
|
- /docs/intro/vs/chef_puppet_etc/
|
2019-08-23 14:22:47 -07:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
Chef, Puppet, Ansible, and Salt are all popular _configuration management tools_. These tools help you install and
|
|
|
|
|
manage software on existing cloud infrastructure, either for bootstrapping a virtual machine, or patching one. They do
|
|
|
|
|
not attempt to solve the problem of provisioning or updating infrastructure, containers, or serverless resources.
|
|
|
|
|
|
|
|
|
|
Pulumi is fundamentally different than these tools and works great alongside them. Pulumi manages provisioning and
|
|
|
|
|
updating of your cloud infrastructure and applications, including virtual machines, containers, databases, hosted
|
|
|
|
|
cloud services, and serverless functions.
|
|
|
|
|
|
Eliminate "real languages" from our website (#4032)
* Eliminate "real languages" from our website
We know that this terminology is unfriendly and can be seen as
gatekeeping. We've moved away from it over time, but there are many
traces of it in our documentation -- most notably, even on our
homepage. Instead of "real languages", let's use "familiar languages",
and in places where deeper explanation makes sense in context, we
can say "familiar, general-purpose languages."
The current 2nd-level blurb on the homepage isn't very good right now
anyhow, so this is a convenient change. As we make progress on various
marketing efforts, we will likely make more extensive changes, but
for now this at least fixes this problem. We recently A/B tested
updates without much of an impact, so let's move ahead with this change
and then if we want to test alternatives to "familiar", we can do that.
For instance, we considered "popular", etc.
* Also eliminate "real code"
2020-08-19 06:19:50 -07:00
|
|
|
Pulumi uses expressive, general-purpose languages, much like some configuration management tools, to define cloud requirements and
|
2019-08-23 14:22:47 -07:00
|
|
|
desired infrastructure state. The Pulumi tool then takes these descriptions and can manage multiple environments to
|
|
|
|
|
ensure that your infrastructure is always up to date, either through its CLI or in a hosted CI/CD scenario.
|
|
|
|
|
|
|
|
|
|
Pulumi works well with modern "immutable infrastructure" architectures, where bootstrapping and patching are
|
|
|
|
|
unnecessary. In such cases, configuration management is not needed in the usual sense. Pulumi also works well with
|
|
|
|
|
classical approaches to infrastructure, however, which often entail virtual machines and where continuing to use a
|
|
|
|
|
configuration tool in conjunction is easy. In either case, Pulumi will help on your path to cloud native architectures.
|
