2 Commits

Include renames

Author	SHA1	Message	Date
3 people	4bb13a5ce8	Fix Ansible 12 double-templating and Jinja2 spacing issues (#14836) ... * Fix Ansible 12 double-templating and Jinja2 spacing issues This PR fixes critical deployment issues and improves code consistency for Ansible 12 compatibility. ## Fixed Issues ### 1. Double-templating bug (Issue #14835) Fixed 7 instances of invalid double-templating that breaks deployments: - Changed `{{ lookup('file', '{{ var }}') }}` to `{{ lookup('file', var) }}` - Affects Azure, DigitalOcean, GCE, Linode, and IPsec configurations - Added comprehensive test to prevent regression ### 2. Jinja2 spacing inconsistencies Fixed 33+ spacing issues for better code quality: - Removed spaces between Jinja2 blocks: `}} {%` → `}}{%` - Fixed operator spacing: `int -1` → `int - 1` - Fixed filter spacing: `|b64encode` → `| b64encode` - Consolidated multiline expressions to single lines ### 3. Test suite improvements Enhanced boolean type checking test to be more targeted: - Excludes external dependencies and CloudFormation templates - Only tests Algo's actual codebase - Verified with mutation testing - Added comprehensive documentation ## Testing - All 87 unit tests pass - 0 Jinja2 spacing issues remaining (verified by ansible-lint) - Ansible syntax checks pass for all playbooks - Mutation testing confirms tests catch real issues 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix Python linting issue - Remove unnecessary f-string prefix where no placeholders are used - Fixes ruff F541 error * Fix line length linting issues - Break long lines to stay within 120 character limit - Extract variables for better readability - Fixes ruff E501 errors --------- Co-authored-by: Claude <noreply@anthropic.com>	2025-09-15 09:54:45 -04:00
3 people	72900d3cc7	Fix Ansible 12.0.0 boolean type checking breaking deployments (#14834) ... * Fix Ansible 12.0.0 boolean type checking issue Ansible 12.0.0 enforces strict type checking for conditionals and no longer automatically converts string values "true"/"false" to booleans. This was causing deployment failures after the recent Ansible version bump. Changes: - Fix ipv6_support to use 'is defined' which returns boolean instead of string - Fix algo_* variables in input.yml to use {{ false }} instead of string "false" - Add comprehensive tests to prevent regression - Add mutation testing to verify tests catch the issue The fix uses native boolean expressions instead of string literals, ensuring compatibility with Ansible 12's strict type checking while maintaining backward compatibility. Fixes #14833 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix Python linting issues in test files - Fix import sorting and remove unused imports - Remove trailing whitespace and blank lines with whitespace - Use underscore prefix for unused loop variables - Remove unnecessary file open mode arguments - Add newlines at end of files - Remove unused variable assignments All ruff checks now pass. --------- Co-authored-by: Claude <noreply@anthropic.com>	2025-09-11 19:32:09 -04:00