-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a dependency for treydock/gpg #143
Comments
is that a _hard_ dependency? |
This isn't hard dependency. In some upcoming pull requests I will get rid of this dependency entirely by using new parameters in yum_repo making Puppet 3.6.x the minimum Puppet version. |
Aside: gpg_key currently appears to be broken when using Facter 2 or above. treydock/puppet-gpg_key#6 |
@igalic is there any documentation re: metadata.json and hard vs soft dependencies? I just spent some time trying to figure out why we were getting I'd assumed that if a module was using metadata.json, that would contain all dependencies, period... |
@jantman http://docs.puppetlabs.com/guides/style_guide.html#dependencies . I wish there was a solution with dependency-sets depending on osfamily, but sadly there isn't at the moment... |
We could agree to set up a hash of 'indirect dependencies' inside metadata.json. cc @ryanycoleman |
On Redhat systems, the
nodejs::repo::nodesource::yum
class uses a customgpg_key
resource type. By default, this module is not specified in the dependency list. It appears to be a hard dependency for yum based package managers.The text was updated successfully, but these errors were encountered: