17f833f27a
At the moment it's possible only to forcefully restart sockets under each run, which is not idempotent and may cause interruptions for service. To avoid that we add a way to restart socket just on config change with same logic applied as for service. Change-Id: Ifb6fd9461d7b6a65191b918c0863406cf4de6725
28 lines
986 B
YAML
28 lines
986 B
YAML
---
|
|
# Copyright 2023, Cleura AB.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
- name: "Restart socket"
|
|
systemd:
|
|
name: "{{ socket.socket_name | replace(' ', '_') }}.socket"
|
|
state: restarted
|
|
when:
|
|
- "'socket_name' in socket"
|
|
- socket.restart_changed | default(systemd_service_restart_changed) | bool
|
|
- "'state' not in socket"
|
|
- socket.enabled | default(systemd_service_enabled) | bool
|
|
loop: "{{ socket_results.item }}"
|
|
loop_control:
|
|
loop_var: socket
|