Think about subs in general, i.e. such that when other groups want to use the framework, they only need to change stuff in one place.
e.g. hosts (like sls-vserv-…) to subs as other groups might use different hosts.
Should catch bugs like:
changing {{ agebd_env }} to {{ agebd_env_suffix }}
test this
Ideally the subs are defined in a yml file and both python and ansible stuff reads from that file so that they are linked. One source of truth only.
Think about subs in general, i.e. such that when other groups want to use the framework, they only need to change stuff in one place.
e.g. hosts (like sls-vserv-…) to subs as other groups might use different hosts.
Should catch bugs like:
changing {{ agebd_env }} to {{ agebd_env_suffix }}
test this
Ideally the subs are defined in a yml file and both python and ansible stuff reads from that file so that they are linked. One source of truth only.
labrec_b
added this to the Benjamin Labrecque project 2026-07-29 13:37:24 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Think about subs in general, i.e. such that when other groups want to use the framework, they only need to change stuff in one place.
e.g. hosts (like sls-vserv-…) to subs as other groups might use different hosts.
Should catch bugs like:
changing {{ agebd_env }} to {{ agebd_env_suffix }}
test this
Ideally the subs are defined in a yml file and both python and ansible stuff reads from that file so that they are linked. One source of truth only.