https://www.puppet.com/community logo
Join SlackCommunities
Powered by
# office-hours
  • d

    Dr Bunsen Honeydew

    05/04/2023, 10:02 PM
    meeting Next up is Content and Tooling in 112 hours
  • d

    Dr Bunsen Honeydew

    05/09/2023, 1:45 PM
    waiting Content and Tooling is about to start up in 15 minutes
  • j

    Jordan Breen

    05/09/2023, 2:00 PM
    Hey everyone 👋 The CAT team will be around for the next hour or so to answer any of your qs cat dance
    👋 2
  • s

    Slackbot

    05/09/2023, 2:00 PM
    This message was deleted.
    j
    r
    +4
    • 7
    • 21
  • s

    Slackbot

    05/09/2023, 2:01 PM
    This message was deleted.
    👀 1
    j
    p
    r
    • 4
    • 42
  • d

    Dr Bunsen Honeydew

    05/09/2023, 2:45 PM
    indeed _🦊Vox Pupuli monthly sync; see calendar event for info_ is about to start up in -15 minutes
  • j

    Jordan Breen

    05/09/2023, 3:00 PM
    Thats all from us for this week, see you again next tuesday 👋 puppet
    👋🏻 1
    👋 1
  • d

    Dr Bunsen Honeydew

    05/09/2023, 3:45 PM
    indeed 🧑‍🏫 Bolt is about to start up in 15 minutes
  • c

    Cas Donoghue

    05/09/2023, 3:59 PM
    Hi, welcome to the time shifted bolt office hour.
    👋🏻 1
    👋 1
  • c

    Chris Reay

    05/09/2023, 4:12 PM
    Hello, We would really like to leverage bolt more in our environment. We manage a Windows fleet of over 6000 nodes but we are only able to use PXP/PCP transport. WinRM is disabled. Because of this, Bolt commands run on Windows via the command prompt and not Powershell which causes us to run into numerous format and syntax issues trying to pass commands through bolt, to the command prompt to powershell. We usually end up relying on other tools like Crowdstrike which have more direct real time console access to Windows systems with Powershell instead. Is this something that has ever been brought up? Is there another way around this or is it possible to fix/change this in the future?
  • c

    Cas Donoghue

    05/09/2023, 4:15 PM
    the pxp-agent should be invoking powershell commands
  • c

    Cas Donoghue

    05/09/2023, 4:16 PM
    when a command is sent to a windows agent over PCP the agent effectively does:
    powershell.exe {your command and args} -NoProfile -NonInteractive -NoLogo -ExecutionPolicy Bypass -Command
  • c

    Cas Donoghue

    05/09/2023, 4:17 PM
    ohhh
  • c

    Cas Donoghue

    05/09/2023, 4:17 PM
    wait you are not using PE to run the plans?
  • c

    Cas Donoghue

    05/09/2023, 4:18 PM
    When you use bolt you are using https://github.com/puppetlabs/puppetlabs-bolt_shim/tree/main/tasks which is a simple ruby task to shell out
  • c

    Cas Donoghue

    05/09/2023, 4:18 PM
    If you want full feature you need to use PE
  • c

    Chris Reay

    05/09/2023, 4:18 PM
    bolt shim command has the same result
  • c

    Cas Donoghue

    05/09/2023, 4:18 PM
    Alternately you could write your own bolt shim
  • c

    Chris Reay

    05/09/2023, 4:19 PM
    we do run powershell in our plans that have powershell but if we need to run one off troubleshooting steps on systems it becomes extremely time consuming to have to convert everything
  • c

    Cas Donoghue

    05/09/2023, 4:19 PM
    pxp-agents modules like command, apply_prep etc are only available to PE
  • c

    Cas Donoghue

    05/09/2023, 4:20 PM
    The integration of bolt with PE for sure could be better, but its a hard proposition for many enterprise users to let users run arbitrary commands on all nodes
  • c

    Chris Reay

    05/09/2023, 4:20 PM
    well it is already possible, just not with powershell 😄
  • c

    Cas Donoghue

    05/09/2023, 4:21 PM
    but the model there is that you still get all the normal RBAC for tasks because you control bolt_shim
  • c

    Cas Donoghue

    05/09/2023, 4:21 PM
    if we remove that we dont have the same auth rules
  • c

    Cas Donoghue

    05/09/2023, 4:21 PM
    So if you trust your bolt user you give them perms for bolt_shim on a subset of nodes.
  • c

    Cas Donoghue

    05/09/2023, 4:23 PM
    I would say that if you want to have a quick easy solution for your use case you can write a powershell implementation for https://github.com/puppetlabs/puppetlabs-bolt_shim/blob/main/tasks/command.json and deploy it
  • c

    Cas Donoghue

    05/09/2023, 4:23 PM
    in your PE env
  • c

    Chris Reay

    05/09/2023, 4:25 PM
    Yes, we are aware we could always write something ourselves. We just wanted to raise it as an issue we are experiencing here. It is not anything that is not already possible using existing Puppet and PE functionality. It is just very difficult to use efficiently in its current state.
  • c

    Chris Reay

    05/09/2023, 4:26 PM
    It is easier for us to use something else because Puppet lacks this functionality out of box
  • c

    Cas Donoghue

    05/09/2023, 4:28 PM
    I would love to see bolt become better integrated with PE. This is a story that fits well into that use case. Appreciate you bringing it up.
    gratitude thank you 1
1...535455...78Latest