In case there's a configuration file present in the sshd_config.d directory then the role configured options do not necessarily get used if the unexpected configuration file has higher priority.
It would nice to be able to have the role to remove all unrecognised configuration files from sshd_config.d. On RHEL, for instance, there might be few non-role configuration files created by security hardening tools such as oscap(8) which would be ok to be left in place whereas something like 0-test.conf or 0-rogue.conf should be removed.
Thanks.
In case there's a configuration file present in the sshd_config.d directory then the role configured options do not necessarily get used if the unexpected configuration file has higher priority.
It would nice to be able to have the role to remove all unrecognised configuration files from sshd_config.d. On RHEL, for instance, there might be few non-role configuration files created by security hardening tools such as oscap(8) which would be ok to be left in place whereas something like 0-test.conf or 0-rogue.conf should be removed.
Thanks.