- 27 Aug, 2015 4 commits
-
-
Marius Gedminas committed
-
Marius Gedminas committed
-
Marius Gedminas committed
-
Note that this test was broken in devel because it was really just duplicating the AES256 test because setting v.cipher_name to 'AES' no longer selected AES after it was de-write-whitelisted. Now that we've removed the VaultAES encryption code, we embed static output from an earlier version and test that we can decrypt it.
Abhijit Menon-Sen committed
-
- 26 Aug, 2015 3 commits
-
-
Abhijit Menon-Sen committed
-
Abhijit Menon-Sen committed
-
Fixes #11981 Fixes #11995 Fixes #12039 Fixes #12077
James Cammarata committed
-
- 25 Aug, 2015 8 commits
-
-
Toshio Kuratomi committed
-
Toshio Kuratomi committed
-
Brian Coca committed
-
added block environment test
Brian Coca committed -
Brian Coca committed
-
Brian Coca committed
-
Brian Coca committed
-
Brian Coca committed
-
- 24 Aug, 2015 1 commit
-
-
James Cammarata committed
-
- 23 Aug, 2015 4 commits
-
-
Rene Moser committed
-
Rene Moser committed
-
Rene Moser committed
-
Closes #8682
Ryan Petrello committed
-
- 22 Aug, 2015 1 commit
-
-
* Add exception handling when running PowerShell modules to provide exception message and stack trace. * Enable strict mode for all PowerShell modules and internal commands. * Update common PowerShell code to fix strict mode errors. * Fix an issue with Set-Attr where it would not replace an existing property if already set. * Add tests for exception handling using modified win_ping modules.
Chris Church committed
-
- 21 Aug, 2015 1 commit
-
-
Brian Coca committed
-
- 19 Aug, 2015 4 commits
-
-
This change is similar to https://github.com/ansible/ansible/pull/10465 It extends the logic there to also support none types. Right now if you have a '!!null' in yaml, and that var gets passed around, it will get converted to a string. eg. defaults/main.yml ``` ENABLE_AWESOME_FEATURE: !!null # Yaml Null OTHER_CONFIG: secret1: "so_secret" secret2: "even_more_secret" CONFIG: hostname: "some_hostname" features: awesame_feature: "{{ ENABLE_AWESOME_FEATURE}}" secrets: "{{ OTHER_CONFIG }}" ``` If you output `CONFIG` to json or yaml, the feature flag would get represented in the output as a string instead of as a null, but secrets would get represented as a dictionary. This is a mis-match in behaviour where some "types" are retained and others are not. This change should fix the issue. I also updated the template test to test for this and made the changes to v2. Added a changelog entry specifically for the change from empty string to null as the default. Made the null representation configurable. It still defaults to the python NoneType but can be overriden to be an emptystring by updating the DEFAULT_NULL_REPRESENTATION config.
Feanil Patel committed -
Rene Moser committed
-
Rene Moser committed
-
Brian Coca committed
-
- 18 Aug, 2015 3 commits
-
-
Brian Coca committed
-
fixes #11979
Brian Coca committed -
Damian Gerow committed
-
- 16 Aug, 2015 2 commits
-
-
Brian Coca committed
-
Brian Coca committed
-
- 15 Aug, 2015 1 commit
-
-
Brian Coca committed
-
- 13 Aug, 2015 3 commits
-
-
Brian Coca committed
-
Brian Coca committed
-
Brian Coca committed
-
- 12 Aug, 2015 2 commits
-
-
Brian Coca committed
-
Brian Coca committed
-
- 06 Aug, 2015 3 commits
-
-
Toshio Kuratomi committed
-
in view of simpler solution incomming from james This reverts commit bae7a02b.
Brian Coca committed -
Fix inventory so this won't happen and fix DataLoader so that it will test relative paths relative to self._basedir Fixes #11789
Toshio Kuratomi committed
-