Pulumi has released version 3.0, a new major release of its eponymous infrastructure-as-code tool. It incorporates feedback from thousands of users and over 200 contributions from more than 150 members of the community. The project remains true to its motto of not forcing cloud engineers into a JSON or YAML corset for their tasks, but rather leaving the choice of implementation language largely up to them.
As Pulumi CTO Luke Hoban describes in a blog post, one component is the newly introduced Automation API. Pulumi can be integrated directly into custom applications and developers no longer have to struggle with the command line. The API works, with all languages supported by Pulumi, like TypeScript.
Pulumi’s new Automation API can be used in a variety of ways.
New providers and distribution methods
Pulumi can handle over 50 cloud and SaaS applications. Since the release of the process version 2.0 last year, the developers integrated about a dozen more providers, such as Civo, Venafi, Okta, Auth0, Equinix Metal, Spot Ocean for Azure and Splunk. For the two coarse there are now native Pulumi providers: for Azure as a finished version 1.0, for Google as preview. The native providers are generated directly from the APIs and resource models of the cloud providers and are also maintained by their development teams. They therefore offer 100% coverage of the API and the quasi-immediate availability of new functions.
The packages have also been enhanced so that resources defined in one language can also be used in all other supported languages. Pulumi 3.0 offers the possibility to define structures of a higher abstraction level than normal Pulumi programs and to distribute them as components.
The new dashboard provides a comprehensive overview of the current infrastructure.
Among many other enhancements described in detail in Hoban’s blog post, there is also a visual innovation. Pulumi now offers a dashboard page with a lot of information about the system. This summarizes information on the infrastructure under consideration for both individual and corporate users.
A detailed article on the subject of open source tools for configuration management can be found in iX 1. It looks at the configuration management systems Ansible, CFEngine, Chef, Fully Automatic Installation, mgmt, Pulumi, Puppet, Rudder, SaltStack and Terraform, as well as the three widely used meta tools Foreman, ManageIQ and StackStorm.