Ansible gcdns_record模块TXT记录数据引号转义问题

I’ve run into this exact problem with the gcdns_record module before—super frustrating when the TXT record ends up with extra quotes or escape characters. Let’s break down what’s happening and how to fix it:

The Problem Recap #

• When you use record_data: "{{ some_var }}", the module throws an error because it strictly requires TXT record values to be wrapped in double quotes.
• If you try escaping quotes like record_data: "\"{{ some_var }}\"", the task runs successfully but you end up with ""your-value-here"" (double double quotes) because the escape characters get preserved in the final DNS record.

Why This Happens #

When you use escaped double quotes inside a YAML double-quoted string, Ansible’s Jinja2 templating and YAML parsing interact in a way that preserves the escape logic, leading to those unwanted extra quotes. The module needs the value to be a single string wrapped in double quotes—not a string with escaped quote characters.

The Solutions #

1. Use Single Quotes to Wrap the Quoted Value

The simplest fix is to wrap your entire Jinja2 expression in single quotes, which tells YAML not to parse the inner double quotes as part of the YAML syntax:

- name: Create valid TXT record
  gcdns_record:
    zone: your-domain.com
    record: _acme-challenge
    type: TXT
    record_data: '"{{ some_var }}"'
    state: present

When this runs, Jinja2 will render some_var, and the outer single quotes ensure the inner double quotes are passed directly to the module. The final value sent to Google Cloud DNS will be "your-actual-value"—exactly what the module expects.

2. Use the quote Filter (More Reliable for Edge Cases)

If your variable might contain special characters, using Ansible’s quote filter is a safer option. It automatically wraps the string in double quotes and handles any internal escaping needed:

- name: Create valid TXT record with quote filter
  gcdns_record:
    zone: your-domain.com
    record: _acme-challenge
    type: TXT
    record_data: "{{ some_var | quote }}"
    state: present

This is especially useful if some_var could have characters that need escaping (like quotes or backslashes)—the filter takes care of all that for you.

3. Predefine the Value in Variables

If you prefer cleaner task definitions, you can build the quoted value in your vars section first:

vars:
  txt_record_content: '"{{ some_var }}"'

tasks:
  - name: Create valid TXT record
    gcdns_record:
      zone: your-domain.com
      record: _acme-challenge
      type: TXT
      record_data: "{{ txt_record_content }}"
      state: present

Verification #

After applying any of these fixes, check your Google Cloud DNS record—it should show up as your-actual-value wrapped in a single set of double quotes, no extra escapes or duplicate quotes.

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