files/file: add support for symbolic permission modes
Update docs to include directories inside group_vars
Added note on which version did dirs in group_vars start working
Adding support for A10 Networks slb server, slb service-group, slb virtual-server
ELB enhancements

* connection draining
* cross AZ load balancing
Adds support for `kern_id` param in ec2_ls module.
Adds RAM disk id support for ec2_lc module.
Adds support for IAM instance profile in ec2_lc module
Adds support for EBS optimized instances in ecl_lc module.
Adds the possibility to attach a public IP address to instances launched into an autoscaling group within a VPC to ec2_lc module.
Adds support for instance monitoring in ec2_lc module.
Issue with printing unicode non-english characters #8425 patch
Unarchive should work when parent directory is not writable

Correct unarchive so that the checks for writeability are
sensible.

Added a test for when parent directory is not writable
PEP8 Compliant except needed long lines and better exception handling
Only chown on atomic move if invoked as root

Linux and BSD derivatives do not allow unprivileged users to
"give away" files to others for security reasons. (System V
derivatives allow that but they're rare nowadays.)
Try optimistic chown, do not error out if not permitted to chown

Add unit test
Fix RDS AWS connection

Use the common AWS connection improvements so that security_token,
boto_profile etc. are taken into account
Added winrm test for long-running command.
$powershellpath is called as ".$powershellpath"

$powershell path is set to "C:\powershell" at line 27. This is fine, but on line 82 $powershellpath is called as ".$powershellpath\$filename". Because the path at line 27 is absolute, a period preceding the $powershellpath is not required at 82. It actually causes an error:

Start-Process : This command cannot be executed due to the error: Unknown error (0x80041002).
At C:\users\Nathan Sosnovske\Documents\ps2to3.ps1:81 char:14

Start-Process <<<< -FilePath ".$powershellpath\$filename" -ArgumentList /quiet
CategoryInfo : InvalidOperation: (:) [Start-Process], InvalidOperationException
FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.Commands.StartProcessCommand
Removing the period on line 82 before $powershellpath fixes this error.
debconf module: add the missing 'error' vtype and reorder vtypes as they appeared in debconf-devel(7).