Not able to configure a mesh about ansible-alertmanager HOT 4 CLOSED

It's not an issue with software. Basically it comes down to 2 things:

1. design of alertmanager, which accepts multiple mesh.peer parameters on command line
2. defining alertmanager_cli_flags as dict, which in turn doesn't allow duplicate/multiple keys

I think we have two ways of fixing it:

1. change alertmanager_cli_flags to store a list of values
2. separate mesh configuration into another variable (ex. alertmanager_mesh) and concatenate it with alertmanager_cli_flags in service template.

For me second way is clearer and maybe will allow us better control, since we could write some preflight checks and notify user if he/she does sth wrong.

from ansible-alertmanager.

It can be an issue with software version (python, ansible) or jinja template. I will try to catch it.

from ansible-alertmanager.

I totally agree with paul - this is a problem of the role and the analysis is correct.

I would also prefer the second way. Also this gives you more flexibility when the configuration of the mesh configuration changes (from the alert manager side). Which most likely will, as it it under active development as described in the readme

from ansible-alertmanager.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from ansible-alertmanager.