寻求Ansible任务：变量不匹配正则表达式时终止Playbook运行

Got it, let's walk through how to build an Ansible task that stops your playbook dead in its tracks when a specified variable fails to match a given regular expression. This is super useful for enforcing input validation before running critical tasks.

Step-by-Step Implementation #

First, we'll use Ansible's built-in fail module combined with the regex_search filter to handle the validation. Here's a complete example:

---
- name: Enforce variable regex validation
  hosts: all
  vars:
    # Example variable - replace with your actual variable
    target_var: "invalid_value!123"
    # Example regex - adjust this to your required pattern
    required_regex: "^[a-z0-9-]+$"

  tasks:
    - name: Check if target_var is defined
      ansible.builtin.fail:
        msg: "Error: 'target_var' is not defined. Please provide this variable before executing the playbook."
      when: target_var is undefined

    - name: Validate target_var against regex pattern
      ansible.builtin.fail:
        msg: >
          Error: 'target_var' value '{{ target_var }}' does not match the required pattern.
          Expected format: lowercase letters, numbers, and hyphens only (pattern: {{ required_regex }}).
      when: target_var | regex_search(required_regex) == None

Breakdown of the Tasks #

• Check variable exists: First we make sure the variable is even defined—this prevents unexpected errors if someone forgets to pass it in.
• Regex validation: The regex_search filter scans the variable's value against your regex. If no match is found, it returns None, which triggers the fail module. The custom error message tells you exactly what went wrong, making debugging a breeze.

Customization Tips #

• Replace target_var with your actual variable name (e.g., server_hostname, database_name).
• Update required_regex to match your specific format:
  • For email addresses: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
  • For IPv4 addresses: ^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$
• Tweak the msg field to provide context relevant to your playbook's use case.

This approach ensures your playbook only proceeds if the variable meets your validation rules, avoiding messy downstream errors from invalid inputs.

内容的提问来源于stack exchange，提问作者DarVar