letsencrypt: Fix graphite02 restart handler
185797a0e5
made graphite01 (old server)
accidentally do the container restart; this should be for graphite02.
Change-Id: I881ffecf9af5ee07cc3ebcf34f0e204a6389d16b
This commit is contained in:
parent
9fdbd56d16
commit
47a57e9939
@ -12,10 +12,10 @@
|
||||
# https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.8.html#imports-as-handlers
|
||||
|
||||
- name: letsencrypt updated graphite01-main
|
||||
include_tasks: roles/letsencrypt-create-certs/handlers/restart_graphite.yaml
|
||||
include_tasks: roles/letsencrypt-create-certs/handlers/restart_apache.yaml
|
||||
|
||||
- name: letsencrypt updated graphite02-main
|
||||
include_tasks: roles/letsencrypt-create-certs/handlers/restart_apache.yaml
|
||||
include_tasks: roles/letsencrypt-create-certs/handlers/restart_graphite.yaml
|
||||
|
||||
- name: letsencrypt updated tarballs-main
|
||||
include_tasks: roles/letsencrypt-create-certs/handlers/restart_apache.yaml
|
||||
|
Loading…
Reference in New Issue
Block a user