win_dsc - be more lenient with datetime parsing (#59703)

* win_dsc - be more lenient with datetime parsing

* Remove l that shouldn't be there

changelogs/fragments/win_dsc-datetime.yaml

@@ -0,0 +1,2 @@
+bugfixes:
+- win_dsc - Be more leniant around the accepted DateTime values for backwards compatibility - https://github.com/ansible/ansible/issues/59667

lib/ansible/modules/windows/win_dsc.ps1

@@ -19,11 +19,7 @@ Function ConvertTo-ArgSpecType {
     $arg_type = switch($CimType) {
         Boolean { "bool" }
         Char16 { [Func[[Object], [Char]]]{ [System.Char]::Parse($args[0].ToString()) } }
-        DateTime { [Func[[Object], [DateTime]]]{
+        DateTime { [Func[[Object], [DateTime]]]{ [System.DateTime]($args[0].ToString()) } }
-            # o == ISO 8601 format
-            [System.DateTime]::ParseExact($args[0].ToString(), "o", [CultureInfo]::InvariantCulture,
-                [System.Globalization.DateTimeStyles]::None)
-        }}
         Instance { "dict" }
         Real32 { "float" }
         Real64 { [Func[[Object], [Double]]]{ [System.Double]::Parse($args[0].ToString()) } }

lib/ansible/modules/windows/win_dsc.py

@@ -54,8 +54,9 @@ options:
       provided but a comma separated string also work. Use a list where
       possible as no escaping is required and it works with more complex types
       list C(CimInstance[]).
-    - If the type of the DSC resource option is a C(DateTime), use a string in
+    - If the type of the DSC resource option is a C(DateTime), you should use
-      the form of an ISO 8901 string.
+      a string in the form of an ISO 8901 string to ensure the exact date is
+      used.
     - Since Ansible 2.8, Ansible will now validate the input fields against the
       DSC resource definition automatically. Older versions will silently
       ignore invalid fields.