is there a Jira issue already for the `warning: al...
# compliancek
kenyon
09/29/2025, 11:12 PMis there a Jira issue already for the
warning: already initialized constant PAM_POSITION_ALIASESlib/puppet/provider/sce_pam/augeas.rbaugeas.rbj
Jason St-Cyr
10/03/2025, 5:04 PMI can see some open tickets about replacing Augeas from a few years back, but I didn't find anything matching the PAM_POSITION_ALIASES error when I did a quick search. Do you have a customer seeing this issue? Would be great to get a support ticket on this.
k
kenyon
10/03/2025, 5:05 PMthanks, yes, I am the customer seeing the issue 🙂 will make a support ticket for it
j
Jason St-Cyr
10/03/2025, 5:06 PMHa, sorry! Yes, please get a ticket in.
k
kenyon
10/03/2025, 5:22 PMCase# 01469093, for the record
keanu thanks 1
kenyon
10/03/2025, 6:07 PMsupport response tried to blame the problem on the Vox Pupuli module, which is where Perforce copied the file from facepalm
kenyon
10/03/2025, 6:10 PMwhy not just depend on augeasproviders_pam rather than copy parts of it in. sce_linux already depends on four Vox Pupuli modules https://forge.puppet.com/modules/puppetlabs/sce_linux/dependencies
kenyon
10/03/2025, 6:18 PM@bastelfreak have you seen this? they also copy a bunch of other files from Vox Pupuli augeasproviders modules: grub, core, mounttab, shellvar, ssh 😒
b
bastelfreak
10/03/2025, 6:19 PMI heard about it. One of the reasons why I would like to switch the vox code to a GPL variant
💯 1
j
Jason St-Cyr
10/06/2025, 12:53 PMI agree, it feels like if the module is needed it should reference the module and not have a copy of it, right? Or have it removed altogether if it's not actually needed anymore. Hopefully the support ticket can help get this fixed by engineering.
b
bastelfreak
10/06/2025, 1:23 PMyes
h
Heston Snodgrass
10/07/2025, 5:04 PMFor posterity, I want to chime in on this. The reason why the code was "vendored" into the SCE modules was because of the long lead time for getting changes merged when it belonged to Herculesteam (I think that's who owned it before Vox). I personally reached out to the point of contact for those modules at the time to let them know what we were doing, as well. Unfortunately, we didn't have the resources to actually maintain those modules or we would have just adopted them. We have done some exploration on replacing that code with our own implementation, but we have not prioritized the effort. However, if this is rubbing y'all the wrong way I can bring this up internally to see if we can either move to the Vox-maintained modules or prioritize our own solution. Our intent was never to cause any issues with the community, we were just trying to solve a problem with the resources we had at the time.
👍 1
❤️ 1
Heston Snodgrass
10/07/2025, 5:05 PMAs for the original issue, I'm raising it internally so we can get this fixed.
👍 1
k
kenyon
10/07/2025, 5:27 PMThanks! As a voxpupuli member, I'd prefer just depending on the Vox Pupuli modules and contributing/helping maintain them.