Add template_yaml parameter to zabbix_template module

[masa-orca]

SUMMARY

• Adding template_yaml parameter to zabbix_template module.
• Using configuration.importcompare to compare template file(not only yaml but also json and xml) with Zabbix current configurations.
• Removing unused functions.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

• zabbix_template

ADDITIONAL INFORMATION

• A type of template_json is not file but json. Therefore, I cloudn't combine template_XXX parameter to a parameter.
• I cloudn't understand that Filter the template json to contain only the keys we will update in filter_template function is needed or not. Let me know if need.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0fc65a5) 79.75% compared to head (5db97f9) 79.54%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1157      +/-   ##
==========================================
- Coverage   79.75%   79.54%   -0.21%     
==========================================
  Files          34       34              
  Lines        4307     4278      -29     
  Branches     1149     1134      -15     
==========================================
- Hits         3435     3403      -32     
- Misses        517      518       +1     
- Partials      355      357       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[flowerysong]

I don't have the time to test it right now, but this shouldn't be necessary.

The point of the json argument type is that it ensures that what the module receives is a consistent format regardless of whether it started as a JSON string or a data structure, so instead of complicating the module interface all you should have to do is convert the file from YAML:

    - name: Import Zabbix template from YAML file.
      community.zabbix.zabbix_template:
        template_json: "{{ lookup('file', 'template4_60_higher.yaml') | from_yaml }}"
        state: present
      register: import_template_yaml

[masa-orca]

@flowerysong Thank you fo your response. I understood it is not necessary. However, it is a temporally workaround that you mentioned way, isn't it?

If this pull request is waste, I'll close it.

[BGmot]

Changelog fragment please?