网上学习资料一大堆,但如果学到的知识不成体系,遇到问题时只是浅尝辄止,不再深入研究,那么很难做到真正的技术提升。
一个人可以走的很快,但一群人才能走的更远!不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人,都欢迎加入我们的的圈子(技术交流、学习资源、职场吐槽、大厂内推、面试辅导),让我们一起学习成长!
- hosts: 172.16.133.129
remote_user: root
tasks:- command: /tmp/test.sh
register: result
这里使用了register寄存器,具体寄存了什么内容,可以使用-v参数来查看输出
- command: /tmp/test.sh
使用ansible-playbook运行
[root@localhost ansible]# ansible-playbook -v test.yml
PLAY [172.16.133.129] *
GATHERING FACTS *******
ok: [172.16.133.129]
TASK: [command /tmp/test.sh] **
changed: [172.16.133.129] => {“changed”: true, “cmd”: [“/tmp/test.sh”], “delta”: “0:00:00.002602”, “end”: “2016-04-11 17:00:57.227517”, “rc”: 0, “start”: “2016-04-11 17:00:57.224915”, “stderr”: “”, “stdout”: “failed”, “warnings”: []}
PLAY RECAP ****
172.16.133.129 : ok=2 changed=1 unreachable=0 failed=0
register保存的信息就时“=>”后面的字典信息,信息保存在result变量中
可以看到"stdout"就是脚本的标准输出信息,这时可以使用"when"来判断是否执行或者跳过
修改test.yml
-
hosts: 172.16.133.129
remote_user: root
tasks:- command: /tmp/test.sh
register: result - file: path=/tmp/test state=directory
when: result.stdout == ‘failed‘
当脚本输出为‘failed‘时就会执行创建目录操作,输出不为‘failed‘,则跳过执行
- command: /tmp/test.sh
执行yml后输出如下:
[root@localhost ansible]# ansible-playbook -v test.yml
PLAY [172.16.133.129] *****
GATHERING FACTS ***
ok: [172.16.133.129]
TASK: [command /tmp/test.sh] **
changed: [172.16.133.129] => {“changed”: true, “cmd”: [“/tmp/test.sh”], “delta”: “0:00:00.002618”, “end”: “2016-04-11 17:11:07.957097”, “rc”: 0, “start”: “2016-04-11 17:11:07.954479”, “stderr”: “”, “stdout”: “failed”, “warnings”: []}
TASK: [file path=/tmp/test state=directory] ***
changed: [172.16.133.129] => {“changed”: true, “gid”: 0, “group”: “root”, “mode”: “0755”, “owner”: “root”, “path”: “/tmp/test”, “size”: 4096, “state”: “directory”, “uid”: 0}
PLAY RECAP ****
172.16.133.129 : ok=3 changed=2 unreachable=0 failed=0
修改test.sh,输出‘success‘,然后执行test.yml
[root@localhost ansible]# ansible-playbook -v test.yml
PLAY [172.16.133.129] *****
GATHERING FACTS ***
ok: [172.16.133.129]
TASK: [command /tmp/test.sh] **
changed: [172.16.133.129] => {“changed”: true, “cmd”: [“/tmp/test.sh”], “delta”: “0:00:00.002611”, “end”: “2016-04-11 17:14:08.456293”, “rc”: 0, “start”: “2016-04-11 17:14:08.453682”, “stderr”: “”, “stdout”: “success”, “warnings”: []}
TASK: [file path=/tmp/test state=directory] ***
skipping: [172.16.133.129]
PLAY RECAP ****
172.16.133.129 : ok=2 changed=1 unreachable=0 failed=0
可以看到当stdout为success时,创建目录的操作直接跳过了
现在回到最终要达到的目的,当脚本输出为‘failed‘时,我们要中断ansible-playbook执行,而不是跳过,这时需要配合fail模块来实现,并且可以抛出自定义信息
修改test.sh文件,输出‘failed‘
修改test.yml
-
hosts: 172.16.133.129
remote_user: root
tasks:- command: /tmp/test.sh
register: result - name: if stdout ‘failed‘ ,Interrupt execution
fail: msg=“check failed”
when: result.stdout == ‘failed‘ - file: path=/tmp/test state=directory
如果脚本执行返回‘failed‘,中断执行,并抛出信息"check failed"
- command: /tmp/test.sh
[root@localhost ansible]# ansible-playbook -v test.yml
PLAY [172.16.133.129] *****
GATHERING FACTS ***
ok: [172.16.133.129]
TASK: [command /tmp/test.sh] **
既有适合小白学习的零基础资料,也有适合3年以上经验的小伙伴深入学习提升的进阶课程,涵盖了95%以上软件测试知识点,真正体系化!
由于文件比较多,这里只是将部分目录截图出来,全套包含大厂面经、学习笔记、源码讲义、实战项目、大纲路线、讲解视频,并且后续会持续更新
试知识点,真正体系化!**
由于文件比较多,这里只是将部分目录截图出来,全套包含大厂面经、学习笔记、源码讲义、实战项目、大纲路线、讲解视频,并且后续会持续更新