Rewrite to implement Ansible roles fititnt.syntactic_sugar & fititnt.faker

[fititnt]

• fititnt.syntactic_sugar
  • https://github.com/fititnt/ansible-syntactic-sugar
  • https://galaxy.ansible.com/fititnt/syntactic_sugar
• fititnt.faker
  • https://github.com/fititnt/ansible-faker
  • https://galaxy.ansible.com/fititnt/faker

---

The current demo version only implements AP-ALB and a few other "infra" modules. Even if add other roles that are more related to infrastructure (like a Galera Cluster for MariaDB/MySQL, maybe GlusterFS as reference to shared storage) this repository would still lack to have some way to implement examples to test.

While AP-ALB itself allows document and implement routing for apps, it neither

1. allow create things like folders, system users, installation of custom PHP-FPM worker
   • For this, fititnt.syntactic_sugar may be an option
2. allow create fake data to simulate real apps
   • For this, fititnt.faker may be an option

This issue here on ansible-linux-ha-cluster may take some time because I need to do some work before on other projects. Maybe at least a few more weeks since I'm doing some non-public work. But breaking in separate reusable roles the way to implement what AP-ALB don't do seems much useful both medium to long run.

The while the fititnt.syntactic_sugar may be too opinionated for ansible veterans, the type of feature of fititnt.faker may be extremely useful for who test in large scale.

[fititnt]

Note (not only to self, but for anyone on future reading this and asking some redundancy): Both fititnt.faker and fititnt.syntactic_sugar have some APIs that are the same (for example a2s_users vs faker_users) but this is both one way to avoid the role fititnt.faker depend on other role and allow end users be very sure about what variables where used only for create fake/testing content and what would be used in production