* The Debian and Ubuntu repositories have slightly changed. You may run into some duplication issues when running the role on a preexisting target that already has had NGINX installed using the role. To fix this, manually remove the old repository source.
* If you use `custom_options` you will now need to manually end each directive with a semicolon.
FEATURES:
* Add support to configure logrotate
* Add support for Ubuntu Focal
* Add support to configure SELinux
ENHANCEMENTS:
* Use `include_tasks` instead of `import_tasks` when possible to speed up the role's execution time
* Improve configuration templating capabilities:
* Add support for unix upstreams
* Add PID templating option
* Add support for down parameter in upstreams
* Add option for custom error pages
BUG FIXES:
*`nginx_debug_output` would sometimes fail if the NGINX had not been automatically started by the system upon installation
* If `http_demo_conf` was undefined the web server template interpolation would fail
This is a relatively minor release, but it includes a potential breaking change (hence the version bump). The one major new feature is the ability to install/build NGINX Open Source from source.
* The new listen templating options are not backwards with the previous listen templating options. Check the `README` or `molecule/template_module/playbook.yml` for examples on how to use the new listen template.
* BSD and Linux NGINX installation tasks have undergone some major changes. As such, you may have to update your playbooks accordingly.
* Module installation when using NGINX Plus has been fixed
* Websockets templating has been reenabled after being accidentally deleted
* When deleting your NGINX Plus license from the system, the NGINX Plus repository will also be deleted to prevent issues further down the line if you run a repository update since there will not be a license anymore to authenticate into the NGINX Plus repository.
* Role should now work correctly in distros with old versions of Python
* Rest API configuration will now only be created when rest_api_enable is set to true (an empty file would be created in previous versions if rest_api_enable was set to false)
* Uploading/dynamically generating files should now result in the files being uploaded/created to/in the correct directory