make entire playbook local #317
Replies: 3 comments 4 replies
|
this is similar to #304, #204 and even #205 I'm not convinced this functionality is needed. Setting --target=localhost will run the playbook against localhost. While this still uses SSH to connect to localhost (requiring SSH server and keys), this is intentional design - it provides consistency in how Spot executes commands regardless of target. If you truly need to run commands locally without SSH, you can:
The current explicit approach has several advantages:
Could you explain your specific use case where the current options don't work? Understanding the actual problem might help find a better solution than adding another global flag or mode that changes fundamental execution behavior. |
The use case is that there will configurations (OS and software tweaks) which will be downloaded from an external source like S3, etc. which will be machine specific.
About the other point ...
How to do this? I am new here, could you point me to an example, thanks in advance. If there is one-and-only-one place where I can add something like |
Uh oh!
There was an error while loading. Please reload this page.
I have discovered
spottoday and seems really nice. 👍I was wondering if there is a way to make the entire playbook "local" and not have to mark every script execution as
local: true.basically mimic the behavior of
ansible-localand run everything locally as the specified user (or current user if not specified)All reactions