New answers tagged

2

There is no error in what you have posted here. The error lies elsewhere in your code which you did not include in the OP. Using the Jinja live parser, when pasting in: {% if spade.corename == 'FI' and spade.nodetype == 'master' %} dataimport-script: file.managed: - name: /opt/bin/DataImport.py - source: salt://files/DataImport.py dataimport-...


0

Most likely, the event driven system you refer to is SaltStack's Reactors and Beacons. As it turns out, Ansible allows the use of Connection plugins to support other transport methods, one of which is SaltStack. This means that there is nothing stopping you from having your cake and eating it too - you can use Ansible to run a playbook using a saltstack ...


0

It feels like what you have done here is implement a discount/bastardized CA (Certificate Authority). I fear that in doing so, you might have inadvertently created a security threat for yourself. In a traditional PKI deployment, your client would generate a private key and a Certificate Signing Request (CSR) that is then submitted to your Certificate ...


0

It looks like you are on the right approach here, the issue seems to be one of debugging. I have found this jinja2 live templating engine to be helpful with debugging in the past. In python (on which jinja is based) "True" is a keyword which is probably getting interpreted as a boolean data type. This would be in contrast to the string, integer, or ...


Top 50 recent answers are included