Fix: Disable privilege escalation for temp file deletion tasks #421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #414
Previously, tasks involving the deletion of temporary files, where delegation to localhost was employed, were unnecessarily requiring sudo privileges. This was causing issues during execution, as the tasks were prompting for a sudo password and failing if not provided.
To address this, we've added
become: false
to these tasks. This disables privilege escalation for these specific tasks, allowing them to execute without needing sudo permissions. It's important to note that this change doesn't affect the security or functionality of our playbook. Instead, it streamlines execution by eliminating unnecessary privilege requests.This fix has been applied to all tasks involving the deletion of temporary files where
delegate_to: localhost
is used.With this update, we expect smoother and more efficient playbook runs, improving our automation capabilities.