fix: add default value to zabbix_proxy_tlsaccept and zabbix_proxy_tlsconnect in create api call argument

[miettal]

null default for these variables was introduced in #1019. But #1291 dropped this. So currently zabbix_proxy role is not working. This PR restore past behavior.

first commit is just adding null default value in defaults/main.yml, but I changed to adding API call argument tasks/main.yml based on review comment in second commit.

see also

• Fix zabbix_proxy role undefined TLS vars #1019
• Clean-up Vars #1291

SUMMARY

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

zabbix_proxy role

ADDITIONAL INFORMATION

[pyrodie18]

I'm confused. What specifically is breaking by not having the variable defined and what does having a null value fix? Just looking through, it looks like everything is handled gracefully with both a undefined and a null value.

[miettal]

see #1019
@loricvdt explained it. @pyrodie18 you are reviewer this PR.

[miettal]

community.zabbix/roles/zabbix_proxy/tasks/main.yml

Line 146 in 5d90497

tls_connect: "{{ zabbix_proxy_tls_config[zabbix_proxy_tlsaccept if zabbix_proxy_tlsaccept else 'no_encryption'] }}"

this line require defenition of zabbix_proxy_tlsaccept, not allowed undefined. // checking defined or not by define() is also solution.

[pyrodie18]

OK then would suggest we do it the right way and sanity check vs just leaving a null value floating.

[miettal]

OK. I'll rewrite PR.

[miettal]

done