Code snippet I shared in question is literally the logic (removing the bash function definition of course which does nothing but writes value of specified variables, and repetitive per db-user lines), not some pseudo-code.
There is no up/down stream. one needs to add/update/remove a tuple when a user is added/updated/removed.
I am just generating alert definitions which will be used by prometheus/ alertmanager (without any further processing what so ever), where team names and DB user names among other things are being edited manually, and will be same way for a long time unless a major overhaul of full system happens. And there is no other developer editing code, depending/ dependent on this script/ yml from any other part of the system.
I would have used format in use already, if there was any other system interaction (completely aligned with "reduce overall system complexity").
Code snippet I shared in question is literally the logic (removing the bash function definition of course which does nothing but writes value of specified variables, and repetitive per db-user lines), not some pseudo-code.
There is no up/down stream. one needs to add/update/remove a tuple when a user is added/updated/removed.
I am just generating alert definitions which will be used by prometheus/ alertmanager (without any further processing what so ever), where team names and DB user names among other things are being edited manually, and will be same way for a long time unless a major overhaul of full system happens. And there is no other developer editing code, depending/ dependent on this script/ yml from any other part of the system.
I would have used format in use already, if there was any other system interaction (completely aligned with "reduce overall system complexity").