Uploaded image for project: 'Puppet Task Runner'
  1. Puppet Task Runner
  2. BOLT-1052

Support run-as for shell localhost transport.

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: BOLT 1.16.0
    • Component/s: None
    • Template:
    • Sprint:
      Bolt Kanban
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      Adds support for `run-as`, `sudo-password`, and `run-as-command` options when running over the local transport on non-Windows nodes. These options escalate the system user (which ran `bolt`) to the provided user, and behave just like the same options using the SSH transport. `_run_as` can also be configured for individual plan function calls for the local transport.
      Show
      Adds support for `run-as`, `sudo-password`, and `run-as-command` options when running over the local transport on non-Windows nodes. These options escalate the system user (which ran `bolt`) to the provided user, and behave just like the same options using the SSH transport. `_run_as` can also be configured for individual plan function calls for the local transport.
    • QA Risk Assessment:
      Needs Assessment

      Description

      To write simple local configuration tooling it's useful to be able to escalate permissions locally.

      This ticket will likely require extracting "shell" action code from the ssh/local/docker transports into a shared location to avoid increasing the amount of duplication.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  lucy Lucy Wyman
                  Reporter:
                  alex Alex Dreyer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support