![]() ![]() Puppet users who want to become advanced practitioners will find everything they expect from a full-featured programming language. In some cases, Puppet users will want to become full practitioners so that they can take greater control of their infrastructure management. This usually comprises most of your Puppet codebase. Most infrastructure will be handled by the descriptive blocks of Puppet code mentioned above. ![]() If you only need a little bit of infrastructure management, your Puppet code doesn’t need to be very complex at all. Puppet is only as complex as you need it to be. You can use the classics like Bash and PowerShell, or Ruby, Python, JavaScript and even good old Perl. What’s more, Puppet supports running tasks written in any scripting language that the target node supports with an interpreter. Your infrastructure code can and should serve as its own documentation. These descriptive blocks are easy to read, with statements like ensure => installed. Most of the Puppet code that you will write will be in the form of descriptive blocks of attributes that say what state a given service or user or other resource should be in. You don’t! The Puppet language is its own full-featured programming language. It’s the bonus myth at the end of the article, if you’re curious. I also want to share one that I personally subscribed to until a couple of weeks ago, despite working at Puppet for almost two years. ![]() As a Puppet educator, I want to share with you some of the myths about Puppet that I encounter when I’m teaching classes, reading Reddit posts or even trying to explain my job to people who are in software but don’t entirely understand what I do. ![]()
0 Comments
Leave a Reply. |