ansible

Commit Graph

Author	SHA1	Message	Date
Sam Doran	c6eff6bdb2	Revert "[stable-2.8] Change default file permissions so they are not world readable (#70221 ) (#70827 )" (#71233 ) This reverts commit `11738aed97`.	5 years ago
Sam Doran	11738aed97	[stable-2.8] Change default file permissions so they are not world readable (#70221 ) (#70827 ) * [stable-2.8] Change default file permissions so they are not world readable (#70221) * Change default file permissions so they are not world readable CVE-2020-1736 Set the default permissions for files we create with atomic_move() to 0o0660. Track which files we create that did not exist and warn if the module supports 'mode' and it was not specified and the module did not call set_mode_if_different(). This allows the user to take action and specify a mode rather than using the defaults. A code audit is needed to find all instances of modules that call atomic_move() but do not call set_mode_if_different(). The findings need to be documented in a changelog since we are not warning. Warning in those instances would be frustrating to the user since they have no way to change the module code. - use a set for storing list of created files - just check the argument spac and params rather than using another property - improve the warning message to include the default permissions. (cherry picked from commit `5260527c4a`) Co-authored-by: Sam Doran <sdoran@redhat.com> * Fix service test * Fix lamdba_policy test * Fix aws_lamdba test * Fix warning for new default permissions when mode is not specified (#70976) Follow up to #70221 Related to #67794 CVE-2020-1736 When set_mode_if_different() is called with mode of 'None', ensure we issue a warning about the change in default permissions. Add integration tests to ensure the warning works properly. * Fix tests - actually use custom module 🤦‍♂️ - verify file permission on created files - use remote_tmp_dir so we're ready for split controller - improve test module so we can skip the call to set_fs_attributes_if_different() - fix tests for CentOS 6 (cherry picked from commit `dc79528cc6`) * Use new category in changelog fragments	5 years ago
Matt Clay	4ea96c151b	Rebalance AWS integration tests in CI.	7 years ago
Dag Wieers	12e7e9650e	Make use of Jinja tests 'finished' (#43233 ) And also used 'changed' and 'failed' tests while we are at it.	7 years ago
Matt Clay	4e489d1be8	Update Shippable integration test groups. (#43118 ) * Update Shippable integration test groups. * Update integration test group aliases. * Rebalance AWS and Azure tests with extra group. * Rebalance Windows tests with another group.	8 years ago
Toshio Kuratomi	abbac1a2ff	Revert "Temporarily comment out tests causing CI errors (#35883 )" This reverts commit `157a41c843`. Have a fix for the underlying issue so reenabling the tests	8 years ago
Sloane Hertel	157a41c843	Temporarily comment out tests causing CI errors (#35883 )	8 years ago
Matt Martz	4fe08441be	Deprecate tests used as filters (#32361 ) * Warn on tests used as filters * Update docs, add aliases for tests that fit more gramatically with test syntax * Fix rst formatting * Add successful filter, alias of success * Remove renamed_deprecation, it was overkill * Make directory alias for is_dir * Update tests to use proper jinja test syntax * Update additional documentation, living outside of YAML files, to reflect proper jinja test syntax * Add conversion script, porting guide updates, and changelog updates * Update newly added uses of tests as filters * No underscore variable * Convert recent tests as filter changes to win_stat * Fix some changes related to rebasing a few integration tests * Make tests_as_filters_warning explicitly accept the name of the test, instead of inferring the name * Add test for tests_as_filters_warning * Update tests as filters in newly added/modified tests * Address recent changes to several integration tests * Address recent changes in cs_vpc	8 years ago
Matt Clay	2ece86fba1	Split up cloud tests to avoid 1 hour CI limit.	8 years ago
Toshio Kuratomi	638de22b35	Update tests for required_if changes These tests are doing string matches on the error condition. Update them to match the new strings. This is probably okay to push out to old releases even though it's technically backwards incompatible because production playbooks won't be checking that a parameter was missing. Param missing is something detected and fixed while writing the playbook.	8 years ago
mikedlr	140ea7f5ff	lambda integration tests - test to show that environment config has an effect (#28815 )	8 years ago
Matt Clay	781fd7099a	Reorganize integration tests: - Move legacy tests into a separate directory. - Reduce common dependencies between targets.	8 years ago
Matt Clay	55fb18b85c	Split cloud tests into two CI groups.	8 years ago
Michael De La Rue	fbec5ab12d	[cloud] new module lambda_policy (PR #24951 ) - Fixes to lambda - reformatting + tests for lambda_facts - lambda module integration test - switch lambda and lambda_facts to AnsibleAwsModule - Get the account ID from STS, GetUser, and finally error message	8 years ago

14 Commits (6ac19b7757670029b895b62c4458e8ad2bc965b3)