guess i will exec it w/ somethign like this command => 'find stuff -name "*.pub" -type f -not -perm 640 -exec chmod 0640 {} \;',

I think I found a PDK bug

This message was deleted.

I ran into a bizzare behavior with a CentOS7 (Or any other Linux) Vagrant puppetserver box running underneath virtualbox on Windows. Line ends of anything puppet touches seem to be getting converted to CRLF which is causing system files such as /etc/sudoers, /etc/ssh/sshd_config, any sort of .sh script , etc to not parse correctly henceforth. Any thoughts on what could cause this?

I ran into a bizzare behavior with a CentOS7 (Or any other Linux) Vagrant box running on Windows. Line ends of anything puppet touches seem to be getting converted to CRLF which is causing system files such as /etc/sudoers, /etc/ssh/sshd_config, any sort of .sh script , etc to not parse correctly henceforth. Any thoughts on what could cause this?

I ran into a bizzare behavior with a CentOS7 (Or any other Linux) Vagrant puppetserver box running on Windows. Line ends of anything puppet touches seem to be getting converted to CRLF which is causing system files such as /etc/sudoers, /etc/ssh/sshd_config, any sort of .sh script , etc to not parse correctly henceforth. Any thoughts on what could cause this?

I ran into a bizzare behavior with a CentOS7 (Or any other Linux) Vagrant puppetserver box running underneath virtualbox on Windows. Line ends of anything puppet touches seem to be getting converted to CRLF which is causing system files such as /etc/sudoers, /etc/ssh/sshd_config, any sort of .sh script , etc to not parse correctly henceforth. Any thoughts on what could cause this?

After running puppet on that VM, things like sudo will break as it can't parse the file, for example running the following command will fix the parsing errors for sudo.

dos2unix /etc/sudoers

Other files such as .sh scripts will just return an error that the file couldn't be found.

This message was deleted.

Corrupted meaning checked in without proper

.gitattributes

protections

These are the worste offenders in that scenario

mod 'saz-ssh', '9.0.0' 
mod 'hardening-os_hardening', '2.3.3'

See the

saz-ssh

module at https://forge.puppet.com/saz/ssh?src=slack&channel=puppet

Those two modules wreck the guest when they're applied (using my Hiera values)

Those two modules wreck the guest when they're applied (using my Hiera values)

I'm not certain whether they use templates or not

They were a pull (via r10k on windows)

What are you using to edit files in windows? I know notepad++ has the option to save files in the Unix format.

I suspect their line ends are getting modified as they're brought down to the windows host via r10k?

Probably. I'd ensure that vscode saves files with *nix line endings and save everything you've edited recently to ensure they all have the proper line endings and re-run r10k.

This message was deleted.

@Yorokobi Windows does have a rudimentary file permissions regime, you just can’t do a whole lot with it, but it does have a concept of owner/group/world and read/write permissions

William is using my personal Vagrant stack, that I've only ever used on Linux or MacOS, https://github.com/natemccurdy/vagrant-puppetserver/tree/control_repo I don't use r10k inside the VM's. Instead, I have the shared

/vagrant

dir symlinked into the production environment: https://github.com/natemccurdy/vagrant-puppetserver/blob/control_repo/vagrant-configs/roles.yaml#L47-L50 This makes the current state of the control repo on your workstation immediately available for Puppet runs in Vagrant, which is really nice. What's odd though is that the CRLF line endings get added to a bunch of files via the shared filesystem, and that happens only on Windows. So I suspect this is more of a Windows + Virtualbox problem than anything else.... but I'm not able to dig too deep since I don't develop on Windows.... like ever.

@CVQuesty that's the other direction I was thinking of going, Were you passing through the SSH parameters for git to the vagrant guest, if so how?

I found a few potential ways to do this, just need to hash it out.

Personally, I wouldn't really codify any of my vagrant-development workflow into my Puppet code/Hiera itself. That's the wrong level of abstraction. Except for maybe a couple of

node

definitions for ephemeral VM's in something like

manifests/vagrant.pp

within the control repo.

When I originally built these, I needed something with a PE master and agents. I used to use these for training. It would allow every user to have the same experience in the class, regardless of their platform. Everything takes place inside the VMs. I haven’t used them as much recently, having spent most of my time in AWS. But they’re all in my GitHub. I tried PE and OSP. PE: https://github.com/cvquesty/centos7-pe2021.2.0 OSP: https://github.com/cvquesty/c7_po6.10.1 Last I checked, these two worked. Thing is, it’s been quite some time, and they both need a little TLC right now, but I can get them working if you want to give them a shot. Just let me know.

This is just for doing content dev as sshing to the master itself isn't a great practice.

This message was deleted.