saltstack-formulas / consul-formula Goto Github PK

I've got the following error when running consul-template with a pillar similar to the example:

    Data failed to compile:
----------
    Rendering SLS 'base:consul-template.config' failed: Jinja variable 'dict object' has no attribute 'template_engine'

Adding template_engine: null to the tmpl section results in errors about the resulting None value.

template_engine: jinja causes jinja syntax errors when trying to read the go template used by consul-template.

I was able to bypass the issue by removing line 15 in consul-template/config.sls: - template: {{ tmpl.template_engine }}

Hi,

setting bind_addr to 0.0.0.0 fails on hosts with multiple IPs.

If you change consul/defaults.yaml:
bind_addr: 0.0.0.0
to
`bind_addr: "{{ grains['ip4_interfaces']['eth0'][0] }}"``
then it will always work.

Not a bug, and not foolproof either. After posting this, I realised just how hard it is to get the 'right' IP from the grains!

Geoff

Hi,

Is it an option to add configuration features :

• "ca_file" -> https://www.consul.io/docs/agent/options.html#ca_file
• "cert_file" -> https://www.consul.io/docs/agent/options.html#cert_file
• "key_file" -> https://www.consul.io/docs/agent/options.html#key_file

Thanks,

Bug details

Describe the bug

Just noticed this when we changed from Centos 7 to Centos 8.
With selinux enforcing, the consul binary moved from /tmp retains the context tmp_t. selinux denies execution of the consul binary so startup fails.

Steps to reproduce the bug

In pillar, set:

consul:
  service: True

Install and try to run consul on a Centos 8 minion.
salt-call state.apply consul

state will fail.

Check the audit log:

grep consul /var/log/audit/audit.log

Expected behaviour

service should start

Attempts to fix the bug

We use the following in install.sls after file.rename fixes the context;

{% if grains['os_family'] == 'RedHat' %}
consul_bin_restorecon:
  module.run:
    - file.restorecon:
        - /usr/local/bin/consul-{{consul.version}}
    - watch:
      - file: consul_install
{% endif %}

Use the module function file.restorecon to change the context of the consul binary to match destination location of the file - which then permits execution by systemd.

Hey, it would be great if you added support for winows agents.

Thanks :)

Hi,

There is a cloud auto-join feature in conusul (https://www.consul.io/docs/agent/options.html#cloud-auto-joining). What do you think about adding support for this feature ?

I can probably do the Pull Request :)

Bye !