Damo Dye

Results 12 comments of Damo Dye

I found this also and opened #686 as I debugged it and found that's it's the regex that causes the issue.

``` TASK [update VM configuration] ************************************************************************************************************************************************************************************************************** task path: /home/ansible/ceh-ansible/proxmox-vms.yml:68 ESTABLISH LOCAL CONNECTION FOR USER: ansible EXEC /bin/sh -c 'echo ~ansible && sleep 0' EXEC /bin/sh -c '( umask 77 &&...

Hi Marcus, thanks for that, the service starts now however am getting the below message now when going to /plugins/azuread/login/ ![Capture](https://user-images.githubusercontent.com/43962340/129153185-9977ddd1-8615-4e14-a30a-3ae460d4e5a2.PNG) any ideas what I have missed ?

ok got that working and I can see in nginx the token comes back but I get this ![Capture](https://user-images.githubusercontent.com/43962340/129176560-7f4276cb-4dfb-4ece-bd2c-b8a6003bda3b.PNG)

ok thats odd because we do have these fields in the directory as a requirement. does this use the values from the token on the LDAP field names. as the...

Hi MarcusThat's for the update I will have a look at it when am next in the office and let you know.RegardsOn 27 Aug 2021 06:20, Marcus Crane ***@***.***> wrote:...

checked module readme and double check. and there is definitely an issue

issue is also happening with max_writers also

>[root@testbox temp-puppet-rhel7]# puppet apply proxysql.pp Error: no parameter named 'max_writers' (file: /root/temp-puppet-rhel7/proxysql.pp, line: 120) on Proxy_mysql_replication_hostgroup[30-31] (file: /root/temp-puppet-rhel7/proxysql.pp, line: 120) on node testbox

ok so I have changed it to > proxy_mysql_group_replication_hostgroup { '30-32-31-33': writer_hostgroup => 30, reader_hostgroup => 31, backup_writer_hostgroup => 32, offline_hostgroup => 33, writer_is_also_reader => 0, max_writers => 1, comment...