v6 update #1
Loading…
Reference in a new issue
No description provided.
Delete branch "v6_update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It updates vagrant, zabbix to v6, the different templates, etc.
Tested on vagrant and proxmox machine.
@ -8,3 +6,1 @@
zabbix_agent: 'true'
zabbix_server: 'true'
zabbix_proxy: 'false'
zabbix_version: '6.0'
We should default to 6.4
6.0 is LTS that is why but OK, I'll change that when all other changes are approved/tested
If its LTS the leave it indeed for the defaults. I thought 6.4 was.
@ -0,0 +1,24 @@
[zabbix]
If its a template it should be templatable otherwise it should be a file IMO.
It would be good to be able to at least adjust
pm
stuff@ -0,0 +31,4 @@
// Uncomment and set to desired values to override Zabbix hostname/IP and port.
// $ZBX_SERVER = '{{ zabbix_server_hostname }}';
// $ZBX_SERVER_PORT = '{{ zabbix_server_listen_port }}';
Why templating those two values if they are commented out?
because there were templated before, but there are commenting out because they were commenting out in upstream new version, so I wasn't sure what to do... If you think that should be uncomment, let me know.
I think if we keep defaults declared then we should uncomment. Or remove it from defaults, and in that case:
Either just remove the vars in the template. or add something like:
{% if zabbix_server_hostname is defined %}
But all that is just details.
done