Closed patemery closed 3 years ago
I figured out what I was doing wrong. Because /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-*
exists in the module data, the merge of my hieradata, which specified "source", was duplicating data provided by the module data causing the error. I simply needed to remove the "source" line from my hieradata. Sorry for wasting anyone's time with this question/issue
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
with the following added locally into the "yum" module. I understand that that is not the right way to do it. I only did it to create the smallest test case I could with the least amount of work.
I added the following to
yum/data/common.yaml
I created a "files" dir in "yum" module and I added the gpg key file from EPEL to
yum/files
directoryWhat are you seeing
What behaviour did you expect instead
I expected
files
dir within modulerpm --import
to run for the file created in /etc/pki/rpm-gpgOutput log
See "What are you seeing above"
Any additional information you'd like to impart
I feel as though I have crafted my yaml correctly to accomplish my goal following the examples in the README. What have I done wrong to cause this compilation/evaluation error?
Sorry if I am using the "issue tracker" here inappropriately. Wasn't sure if this was an acceptable use
First time posting an "issue" on github. I wanted to assign the "question" label to this "issue". I can't seem to do that. Are labels only applied by the project owners?