With Y users requiring access under their own unique accounts,
And not all Y users are required on every X server (although this isn’t a hard requirement),
And Z of the Y users need to be in a different group (for more access or sudo rights based on group),
And each user having their own authorized key file for SSH…
What would be the recommended approach in the structuring of the playbooks/tasks? I’ve thought through a few different solutions (using --extra-vars for example to pass in on a per-user basis the variables needed, or using with_items) but it felt “kludge-y” when attempting to implement…
And each user having their own authorized key file for SSH…
What would be the recommended approach in the structuring of the playbooks/tasks? I’ve thought through a few different solutions (using --extra-vars for example to pass in on a per-user basis the variables needed, or using with_items) but it felt “kludge-y” when attempting to implement…