Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

[Description of the issue]
rsyslog_included_config_template_path variable have double slash when concatenate:

rsyslog_include_config_path: /etc/rsyslog.d
rsyslog_included_config_template_path: "{{ playbook_dir }}/templates/{{ rsyslog_include_config_path }}"

Prerequisites

• [ X ] Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

If RSYSLOG was installed after role was launched, but the service is not enable, it's impossible to enable that service

Steps to Reproduce

1. Launch this role on instances with rsyslog previously installed (but with the service disabled)
2. Check that the service is not enabled

Expected behavior: It would be nice if we provide a way to configure if service should be enabled or not

Actual behavior: Service is enabled only if rsyslog is installed

Reproduces how often:
100%

Versions

1.0.0

Description

We have created a playbook that runs on ubuntu:focal image and it fails the idempotency at the point of "Ensure rsyslog dirs exist".
After "Install rsyslog core package", on ubuntu the directories have syslog:adm permissions, and on debian they have root:root permissions.

• Fix order in installing tasks because idempotency problems.
• Updated tests dependencies: ansible, molecule, docker, ansible-lint.
• Updated Dockerfile: to work on debian and ubuntu.
• There is no .gitattributes file: https://github.com/idealista/jira_role/blob/master/.gitattributes
• There is no travis email notification config: https://github.com/idealista/jira_role/blob/master/.travis.yml#L20-L25
• Some versions in the Pipfile could be updated, at least the patch version (be aware to not break CI): https://github.com/idealista/jira_role/blob/master/Pipfile

Why is this needed?

Then the role will work correctly on both debian and ubuntu.

Additional Information

N/A

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

At this moment, if rsyslog_user is defined, it's created invariably with /bin/false shell. Even when it is a good security practice, it can be an issue in some situations i.e. when rsyslog_user is root. It is needed a fix in order to select the proper shell for the user.

Steps to Reproduce

1. Define rsyslog_user: root
2. Run the playbook

Expected behavior:
root runs rsyslog without user config modifications

Actual behavior:
root runs rsyslog, but root has now a /bin/false shell

Versions

It happens always in all versions

Additional Information

N/A

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

Update requirements versions: ansible, molecule, goss... and update metadata.

Additional Information

Security fixes.

Description

[Description of the issue]

Add log files permissions with variable and general config template as a variable.

Why is this needed?

[A clear and concise description of why do you think this is needed]

General config in rsyslog is not easy to edit.

Additional Information

[Any additional information, configuration or data.]

Not breaking change in the role, just added configuration as variables

Prerequisites

• [ X] Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

Because the role loads the full package names (with major, minor and build versions) with include_vars from vars directory, it's difficult to get updates using the same role because variable precedence. I think it's more useful to store in that vars only the name of the package, and allow setting versions via host/group vars, etc.

Prerequisites

• [ X ] Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aidealista
  • Checked that there is not already provided the described functionality

Description

Currently this role doesn't support Debian Jessie because 8.24.0-1 version isn't available in APT repositories. Last version available for Debian Jessie is v8.4.2.

Steps to Reproduce

1. Launch this role on a Debian Jessie instance
2. It fails because rsyslog v8.24.0-1 isn't available in APT

Expected behavior: Rsyslog is installed

Actual behavior: It fails

Reproduces how often: 100%

Versions

<= v1.1.0

Additional Information

https://packages.debian.org/jessie/rsyslog