In the README.md, it's not explaine that to enable auth on the API, you need :

• es_enable_xpack
• es_api_basic_auth_username
• es_api_basic_auth_password

So to enable auth on the API, you have to set this :

es_enable_xpack: true
es_api_basic_auth_username: elastic
es_api_basic_auth_password: MyPassword

It will be nice to add this block in the README.md to save time of Adsy

I love the community grouping feature with facebook and actually figured out it is at least also possible with whatsapp. It would be awesome if that ended up in the documentation.

Might actually send it in myself if I get the time :)

Hello, just a friendly feedback : it took me an unusually long time to figure out why psql couldn't connect to a PG server deployed using values taken in tests/vars.yml.

Postgres default famous port is 5432, so what is the rationale behind setting it to an unusual value like 5433 ?

➡️ https://github.com/ANXS/postgresql/blob/master/tests/vars.yml#L4

This probably has something

TASK [thefinn93.letsencrypt : install certbot from backports] ********************************************************************************************
[DEPRECATION WARNING]: Invoking "apt" only once while using a loop via squash_actions is deprecated. Instead of using a loop to supply multiple items and
 specifying `pkg: "{{item}}"`, please use `pkg: ['certbot']` and remove the loop. Th

Fix statement condition on "Install custom OpenWISP 2 Python packages" task in pip.yml:

TASK [openwisp.openwisp2 : Install custom OpenWISP 2 Python packages] **********
[DEPRECATION WARNING]: evaluating 'openwisp2_python_packages' as a bare 
variable, this behaviour will go away and you might need to add |bool to the 
expression in the future. Also see CONDITIONAL_BARE_VARS configur

What am I looking for?

Is there anywhere some documentation in how to convert existing nginx configurations to be able to deliver them by this role?

I would for example like to have an example how how to do this with this role.. I haven't been even close yet 😄

/etc/nginx/sites-available/example.com.conf

server {
	listen 443 ssl http2;
	listen [::]:443 ssl http2;

	serve

I've been tasked with creating a CIS Level 1 standard RHEL image in Azure. I've taken a market place RHEL 7.3 image and applied this playbook with packer/ansible using tags level1.

However, when I go and try and create a VM from the image, it fails. If I skip cis_section1, I can create a VM from the image. I'm a linux newbie, apologies, but any obvious rules in section 1 that could be causing

I am attempting to set up a cluster with a mix of arm64 and amd64 nodes. Inventory:

---
all:
    consul:
      vars:
        consul_autopilot_enable: true
        consul_group_name: consul
      hosts:
        host1:
          consul_node_role: bootstrap
          consul_architecture: amd64
        host2:
          consul_node_role: server
          consul_architecture: arm64

currently, we hard-code the default RHEL NTP servers.

According to the documentation for http_publish_uri the wildcard address 0.0.0.0 is only permissable if set via $http_bind_address. Which is the default if http_publish_uri remains unset. For default in the role http_publish_uri is set to "http://0.0.0.0:9000" which is an invalid value. The graylog-server defaults to the, probably first, non-loopback ipv4 address, however it logs this fact every s

#188 is an example where we fail because we reload and not restart tor after the torrc file changed.

Lets enumerate all these cases and add it to the documentation (or decide that restarting is the better option)

The main README file is well done, but I had to take a look under the hood to discover that it is also possible to configure the email server settings 😄

Please add an "Email server" section on the README.

While deploying an Enterprise Vault/Consul Cluster for a customer, I discovered the following issue.

While setting up vault_checksum_file_url to the location where to find the Enterprise checksum for Vault Enterprise binary, which by default is set to https://releases.hashicorp.com/vault/{{ vault_version }}/vault_{{ vault_version}}_SHA256SUMS for OSS which is the file itself. I encountered

@jspaleta mentioned this idea to me during the Summit, we should provide a support Ansible Callback plugin that can be used to report the results of the Ansible run to Sensu.

Datadog has a callback plugin that is pretty sweet here: https://github.com/DataDog/ansible-datadog-callback

Docs: https://docs.ansible.com/ansible/latest/dev_guide/developing_plugins.html#callback-plugins

This is version 1.8.0, commit: b8163a192467da3e665c736f6c67e314a7089804.
If an ipv6 address is specified for the nomad_advertise_address, then nomad will error out with a bind: invalid argument error.

As can be seen in the basic.hcl the problem is that the ports are simply being appended to the nomad_advertise_address. IPv6 syntax requires that the IP portion be placed within brackets - e.g

The link to the CIS guide doesn't work anymore.

On their current version of this it, the ubuntu 16 guide is hidden behind an email registration here: https://www.cisecurity.org/benchmark/ubuntu_linux/

The page is branded for Ubuntu 18, and has a back link for Ubuntu 14, but if you register, you get an email with a link to a download archive where Ubuntu the Ubuntu 16 PDF is available.