Puppet Community

those operations a bit different though - we use the strike-through in places where you can batch a set of changes

the cert accept/reject is an immediate operation

oh absolutely, I have just clicked on the wrong line more than once :rolling_on_the_floor_laughing:

and the only alternative is refreshing the page after every reject or accept

so, upon reject, use the strike, that makes sense

how about just updating the background color of the text to a light green on sign and a strike/light red on reject (strike to deal with colorblindness)

maybe, changing the background color changes the color contrast ratios between foreground and background - might need to futz around with that a bit

UI is 1000% not my thing :smile: but it seemed like a way to give an indication without losing readability or making things disappear

Yeah, not really in my wheelhouse either, but the accessibility requirements are :wink:

I would think that having a status field that says signed/unsigned/rejected could help

So anything done would not interfere with a screen reader, it would mostly be making it clear and not color blind triggering

yeah, that and there are some specific rules around the contrast ratio between foreground and background colors (4.5:1)

just some other visual indication of which one you just select

OK, that’s a wrap for today. Thanks for the suggestions! We’ll be back in a couple of weeks. Y’all be good to yourselves in the meantime!

:goodnews: Next up is _:teacher:Puppet Core Team_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20220524T170000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|115 hours>

you can tell code manager to call the classifier to update all classes <https://puppet.com/docs/pe/2019.8/code_mgr_customizing.html#config_post_env_hooks|https://puppet.com/docs/pe/2019.8/code_mgr_customizing.html#config_post_env_hooks>

:the_more_you_know: _:teacher:Puppet Core Team_ is about to start up in 15 minutes

Hi folks, Core office hours are open! Have a question about open source puppet or Puppet Platform 6 &amp; 7 releases, ask away!

<@U11567REE> can you give <https://github.com/puppetlabs/puppet-agent/pull/2201|https://github.com/puppetlabs/puppet-agent/pull/2201> a look?

:businessparrot: Next up is _:teacher: Bolt_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20220524T220000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|4 hours>

Alright folks that's a wrap, see you in two weeks!

:coffee: _:teacher: Bolt_ is about to start up in 15 minutes

Hello y'all! Bolt office hours are open! If you have a question about Bolt ask away! :boltymcboltface:

Can you elaborate a bit? Not sure I follow.

`bolt command run 'powershell.exe -command "get-process"'`

instead of being able to run powershell directly

for simple commands, it's not too big of a deal but for more complex powershell commands, syntax becomes challenging

I usually resorting to using another tool or platform such as CrowdStrike so I can run powershell directly on a device instead of having to deal with the headache of translating everything to use in Bolt

When Bolt connects to targets, you'll be dumped into whatever the default shell is. For SSH that's _usually_ a bash-like shell, for WinRM that's usually PowerShell. The SSH transport lets you configure a `login-shell`, which you can set to `powershell`. <https://puppet.com/docs/bolt/latest/bolt_transports_reference.html#login-shell>

what if we are only able to use PCP transport since SSH and WinRM are disabled in our environment?

We are not using inventory either. Only using orchestration to connect via PXP/PCP

Unfortunately no way to do that currently, and nothing on our roadmap to support that. It's a good idea, though. Feel free to file a feature request in the Bolt repo: <https://github.com/puppetlabs/bolt/issues/new/choose>

That's a wrap on Bolt office hours! Our next scheduled office hours are on June 14. Until then, feel free to ask any questions you have over in <#C7GP57T50|> ! :boltymcboltface:

:beaker: _:teacher:Puppet Forge_ is about to start up in 15 minutes

This is a really good idea. Would you want it on the module feed itself, or do you think there should also be another feed for all deprecations?

you'd probably want to poke <@U9M9GM5DK> about that particular question, he asked it late last night

if you want my opinion, it's that :smile:

Both is good. I'll file that ticket in just a moment

usually you have the rss feed of a module so it would be good if that feed has the deprecation info

Add on to the ticket if you’d like, <https://tickets.puppetlabs.com/browse/FORGE-641>

Thanks for picking this up and creating the ticket. I’ve voted for it :slightly_smiling_face: