- Dec 04, 2017
- Nov 30, 2017
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-1028831
-
- Nov 28, 2017
-
-
Tejas authored
- For some localle, where output encoding is not utf-8(ex. japan shift_jis), the output of powershell cannot be correctly interepreted when umarshalling json - This causes some characters to be garbled - Use UTF 8 encoding for output cr https://cr.amazon.com/r/8019892/
-
- Nov 27, 2017
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-995798
-
- Nov 23, 2017
-
-
Gabriela Botea authored
Before we refactor the logging messages, instead of confusing customers with an error message and then a success, we only keep this error in traces. In case this error persists, it will be caught in traces. sim: https://issues.amazon.com/issues/birdwatcher-597 cr https://code.amazon.com/reviews/CR-997660
-
- Nov 18, 2017
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-972469
-
- Nov 17, 2017
-
-
- Nov 16, 2017
-
-
- Nov 15, 2017
-
-
-
Shivam Bharuka authored
-
-
- Nov 14, 2017
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-948695
-
Wang authored
-
- Nov 13, 2017
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-941296
-
- Nov 10, 2017
-
-
Marius Nicolae authored
cr https://cr.amazon.com/r/7956970/
-
Wang authored
cr https://code.amazon.com/reviews/CR-926634
-
Wang authored
-
- Nov 08, 2017
-
-
- Nov 07, 2017
-
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-909537
-
Wang authored
-
Wang authored
cr https://code.amazon.com/reviews/CR-902661
-
-
- Nov 02, 2017
-
-
Wang authored
cr https://code.amazon.com/reviews/CR-854894
-
- Oct 31, 2017
-
-
- Oct 30, 2017
-
-
-
-
Bharuka authored
cr https://code.amazon.com/reviews/CR-858548
-
- Oct 28, 2017
-
-
Bharuka authored
cr https://code.amazon.com/reviews/CR-856855
-
- Oct 27, 2017
-
-
Tejas authored
- Windows 2008(R1) uses a different mechanism for managing roles, which has been deprecated from 2008 R2 onwards. Try using that to collect roles - Windows 2003 have different concept of server roles. Try getting roles from registry in such cases - Windows 2003 seems to add unexpected line breaks from powershell output and might cause problem. So swap the cleanup steps cr https://cr.amazon.com/r/7881005/
-
Chan Jeon authored
Correct the version to 2.2 in Config and modified the version generation logic to depend only on the package version cr https://code.amazon.com/reviews/CR-854892
-
Wang authored
cr https://code.amazon.com/reviews/CR-854221
-
Bharuka authored
cr https://code.amazon.com/reviews/CR-799929
-
Bharuka authored
cr https://code.amazon.com/reviews/CR-800080
-
Bharuka authored
cr https://code.amazon.com/reviews/CR-799897
-
Bharuka authored
cr https://code.amazon.com/reviews/CR-761411
-