Automation worst practices
bedlam
Web site and application development is becoming increasingly reliant on automation for building, testing, and deployments. But since practically anything can be automated, it's quite possible to use automation to subvert best practices faster and more effectively than ever before.
To keep that from happening, we need to make sure our scripts, robots, and tools are held to the same high standards we hold ourselves and our colleagues to. But to do that, we have to familiarize ourselves with some of the common problems that make our automated tasks less safe, secure, reliable, and performant than they should be. We need, in other words, to study the Worst Practices, and find out how it all went wrong.
We'll use Drupal and Ansible-oriented examples to describe common types of problems, their causes, effects, and general solutions.
Learning Objectives
At the end of this session, attendees will be able to
- recognize some common automation worst-practices,
- replace anti-patterns in their own automated tools and systems,
- design better quality automation for themselves and their clients.
Target Audience
The session is intended for those who are interested in and/or responsible for developing and maintaining systems and tools for building, testing, and deploying applications.
Prerequisites
This session is suitable for attendees with some experience deploying Drupal to remote environments, or remotely provisioning servers, especially with tools such as Ansible.
Track
DevOps & Infrastructure
Experience Level
Intermediate
When & Where
Time:
Thursday, 16 July, 2020 - 18:15 to 19:00
Room:
Hopin Sessions
If no timezone is set on your profile, time is displayed in UTC.
Update your profile's timezone
