u/chief_wrench

Dear architects,

I am a system administrator in a team, we work a lot with Ansible. In my team we have two approaches to write roles/playbooks:

• One style has ready-made flat configuration files, maybe a few substitutions here and there. Changes might require finding multiple occurences of a string, and replacing them. The Ansible code is copying files for the most part.
• The other style leans heavily on a bunch of lists/dictionaries which I would describe as a "model" of the various object classes of e.g. a company. The Ansible code is written smart enough to derive everything from that model. Fluctuation in the company is reduced to updating the lists/dictionaries.

I am fairly certain that there is a snappy name to distinguish those two approaches.