- Document user passwords in group_vars/all.yml section
- Add important warning about configuring passwords before preinstall
- Include clear instructions for password customization
- Explain automatic hashing behavior
- Change passwords in group_vars/all.yml to clear text (Oracle123, Grid123)
- Use password_hash('sha512') filter in users_configuration.yml for automatic hashing
- Maintain same security level but with more readable and maintainable passwords
- Passwords are hashed automatically during playbook execution
- Add oracle_user_password and grid_user_password to group_vars/all.yml
- Update users_configuration.yml to use password variables instead of hardcoded hashes
- Enable centralized password management for system users
- Keep passwords as clear text variables (no encryption needed for this use case)
- Create clean branch for user password implementation
- Will add oracle and grid user passwords to group_vars/all.yml
- Will update users_configuration.yml to use these variables
- Replace directory existence check with directory creation
- Ensure proper ownership (oracle:oinstall) and permissions (0755)
- Remove failed_when that was causing unnecessary failures
- Make postinstall role more robust for different environments
- Check if inventory.xml exists before grep operation
- Handle first installation scenario properly
- Add informative messages for different installation states
- Use more robust comparison (-ge 1 instead of == 1)
- Add dbhome variable to group_vars/all.yml for consistency
- Remove duplicate Oracle variables from oracle-db-install defaults
- Standardize oracle_home definition across all roles
- Keep only role-specific variables in individual role defaults
- All common variables now centralized in group_vars/all.yml
- Extract common Oracle variables from role defaults to group_vars/all.yml
- Variables are now shared across all roles without duplication
- Maintains backward compatibility with existing role defaults
- Follows Ansible best practices for variable organization
- Create handlers/main.yml for systemd and cron service management
- Use notify to trigger daemon reload after systemd service changes
- Improve service lifecycle management
- Enhance systemd service template with proper User/Group/Environment settings
- Use variables in cron cleaner script instead of hardcoded paths
- Add comprehensive path validations before operations
- Create validations.yml for prerequisite checks
- Improve service dependencies and startup order
- Split main.yml into modular files: scripts.yml, backup.yml, services.yml
- Use include_tasks for better organization and maintainability
- Group related tasks by functionality
- Improve code readability and reusability
- Replace 4 separate git tasks with a single consolidated task
- Add proper error handling with failed_when condition
- Remove ignore_errors usage that was masking real errors
