🐛 Bug - OS/Distro specific built-in users spread to different(wrong) OS #13
	
		Labels
		
	
	
	
	No labels
	
		
			
	
	bug
		
			duplicate
		
			enhancement
		
			good first issue
		
			help wanted
		
			invalid
		
			question
		
			todo
		
			todo 🗒️
		
			wontfix
		
		
	
		No milestone
		
			
		
	No project
	
		
	
	
	
	
		No assignees
		
	
	
		
			
		
	
	
	
		1 participant
	
	
		
		
	Notifications
	
		
	
	
	
		
	
	
	Due date
No due date set.
	
		Dependencies
		
		
	
	
	No dependencies set.
	
	
		
	
	
		
			Reference
		
	
	
		
	
	
			stationgroup/ansible-experiments#13
			
		
	
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	
	No description provided.
		
		Delete branch "%!s()"
	 
	Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
My
ubuntuuser/configs for Ubuntu on EC2 end up on my FreeBSD instances. Same with theec2-userin the FreeBSD AMI.I know, you're probably thinking "Oh not again, you're doing it wrong". Please advice what method I should be using if this was completed.
List of global users:
rememberdirectdegreesandgriefjamkingExclusive users:
ubuntu(Ubuntu AMI)ec2-user(FreeBSD AMI)vagrant(FreeBSD, Ubuntu, Debian, etc)Can you show your inventory and how you configure for this? (/cc @vincentvdk)
(Click to expand `hosts` inventory)
(Click to expand `ansible.cfg`)
I added had to add the privilege escalation in the roles to fix broken/erroring FreeBSD stuff (Ubuntu always worked fine).
I've copied the stuff below from the comment in the
ssh_configfile Issue: https://github.com/stationgroup/ansible-experiments/issues/11#issuecomment-422962420(Click to expand group_vars/all)
I'm using:
as per PR #12
I've made some minor changes to fix issues a chicken and egg issue with FreeBSD. But nothing that should have broke ssh_config.
(Click to expand roles/users/tasks/users.yml)
Resolved ✅