Spearhead/ansible-check_mk
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fixed typo in readme

Browse Source 
the correct syntax is “[…] -u username -s” for running the
ansible-playbook with sudo
This commit is contained in:
Marius Pana 2015-10-28 20:10:38 +02:00
parent 0a123abbcb
commit 73d71225e3
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -41,7 +41,7 @@ Notice the use of the --skip-tags switch which is necessary as in this first run
You now need to create an Automation user in our Check_MK site and use that information in the roles/omd/vars/main.yml file. You now need to create an Automation user in our Check_MK site and use that information in the roles/omd/vars/main.yml file.
Now we can deploy the check_mk_agent to our monitoring instance as well. Notice we are running just the check_mk_agent, discovery and pply steps now. Also after bootstrapping your system you can use your own user if you created one and uploaded the ssh keys. In this case you could use ansible with sudo (-u <username> -s instead of -u root). Now we can deploy the check_mk_agent to our monitoring instance as well. Notice we are running just the check_mk_agent, discovery and pply steps now. Also after bootstrapping your system you can use your own user if you created one and uploaded the ssh keys. In this case you could use ansible with sudo (-u *your_username* -s instead of -u root).
> ansible-playbook -i cmkconfinv site.yml -l omd -u root --tags check_mk_agent,check_mk_discovery,check_mk_apply > ansible-playbook -i cmkconfinv site.yml -l omd -u root --tags check_mk_agent,check_mk_discovery,check_mk_apply