Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: BOLT 0.17.0
    • Component/s: None
    • Labels:
    • Template:
    • Sprint:
      Bolt Kanban
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      Bolt now includes a local transport for taking action on your local machine. It can be targeted via the plain string 'localhost' or using the 'local://...' protocol. Note that anything after 'local://' will be ignored. Also if 'localhost' is a node or group in your inventory, it will override the shortcut for the local transport.

      *Docs site additions*
      Configuring Bolt: the local transport uses the 'tmpdir' config options: it will copy scripts and tasks to a temporary directory before executing, and run all actions in that temporary directory. Use the 'tmpdir' flag to declare a specific directory.
      Running Bolt commands: 'localhost' or 'local://...' can be used to run a command locally. We should update everything to be more agnostic about declaring a transport via the protocol. Currently it says, if using WinRM specify 'winrm://...'.
      Running tasks and plans with Bolt: ditto
      Bolt command options: Everywhere we talk about WinRM, probably also mention the Local transport. Since we'll also be adding information on the PCP transport, this may be the time to talk about transports as a general thing and consolidate on a single section that talks about the different options and relevant differences for them.
      Show
      Bolt now includes a local transport for taking action on your local machine. It can be targeted via the plain string 'localhost' or using the ' local://...' protocol. Note that anything after ' local://' will be ignored. Also if 'localhost' is a node or group in your inventory, it will override the shortcut for the local transport. *Docs site additions* Configuring Bolt: the local transport uses the 'tmpdir' config options: it will copy scripts and tasks to a temporary directory before executing, and run all actions in that temporary directory. Use the 'tmpdir' flag to declare a specific directory. Running Bolt commands: 'localhost' or ' local://...' can be used to run a command locally. We should update everything to be more agnostic about declaring a transport via the protocol. Currently it says, if using WinRM specify ' winrm://...' . Running tasks and plans with Bolt: ditto Bolt command options: Everywhere we talk about WinRM, probably also mention the Local transport. Since we'll also be adding information on the PCP transport, this may be the time to talk about transports as a general thing and consolidate on a single section that talks about the different options and relevant differences for them.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Executing tasks locally is a powerful method of extending the plan language without writing ruby. Currently bolt has to connect over a normal transport to execute local tasks. Instead bolt should have a special local transport that can be used.

      Users can target the local transport with the bare string "localhost"
      Users can target localhost with the protocol 'local'. The rest of the uri will be ignored.

      Implementation:
      Windows and linux code should be kept in separate classes with the executor deciding which version to load/use.
      The Inventory should be responsible for handling the host named 'localhost' and returning a host with the local transport.
      The task should be copied to a tempdir before execution and that tmpdir should be cleaned up.
      If 'localhost' is defined with a different transport in inventory that should override 'localhost' matching.

      Out of scope:
      Windows implementation. local transport should support unix environments and error cleaned if it's used on windows

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  kate.lopresti Kate Lopresti
                  Reporter:
                  alex Alex Dreyer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: