We have a central code. If anyone makes any changes to the infrastructure, we'll get notified. We have around 10 people all managing the same infrastructure so there's always the chance of overstepping each other's work. When it's all centralized as a code, a single repository, it's easier to manage because everybody gets notified of what changes are being made.

Puppet has help us to make the Linux Clients compliant with the Security requirements, independently where are located and the Operative Linux System release.

All of the infrastructure patching and provisioning was done using Puppet.

We used to have lot of issues related to sudo rights on server. Now, we have centralized sudo file managed by puppet on a centralized linux server. So, any of user requests for addition or removal of sudo access, we make changes on puppet master for specific requested node and changes get pushed to puppet client on next cycle.

Puppet Enterprise has reduced the time of production changes or environment changes. It is reducing the time that the engineers spend applying changes of our infrastructure. They set it all up, the next environment, and after they have been tested, when they have to promote a change, they just apply it, and it's turned on on many of hundreds of open sub-ports. To do it manually, reducing the operative time, is a really big part. I think that's the most valuable thing, because your engineers use their time with creative things, visionary things, not doing repetitive tasks.

This product has vastly increased our company’s release management and product stability functionalities.