You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this worked with previous versions of r10k, we have never intentionally/explicitly supported the use of a nil basedir.
In order to fix this issue, we recommend updating the instantiation to one of the following, depending on your needs:
If path and puppetfile are relative paths, they will be resolved relative to the basedir. If they are absolute paths, basedir should be ignored for your particular use case.
Apologies for the breakage! but I want to make clear that we do not consider the internals of the r10k lib to be public API, so things could potentially 'break' without a major version bump.
The text was updated successfully, but these errors were encountered:
A recent update to r10k started causing
TypeErrors
when using kitchen-puppet (see puppetlabs/r10k#1188).This is because you explicitly instantiate
R10K::Puppetfile
with a nilbasedir
: https://github.com/neillturner/kitchen-puppet/blob/master/lib/kitchen/provisioner/puppet/r10k.rb#L50While this worked with previous versions of r10k, we have never intentionally/explicitly supported the use of a nil
basedir
.In order to fix this issue, we recommend updating the instantiation to one of the following, depending on your needs:
OR
If
path
andpuppetfile
are relative paths, they will be resolved relative to thebasedir
. If they are absolute paths,basedir
should be ignored for your particular use case.We've deprecated some params, as seen here: https://github.com/puppetlabs/r10k/blob/ded1045f29f99a624c19eae25d96217cd0dee179/lib/r10k/puppetfile.rb#L53-L58
We'll be updating that yardoc to be clearer about how each param is used.
Apologies for the breakage! but I want to make clear that we do not consider the internals of the r10k lib to be public API, so things could potentially 'break' without a major version bump.
The text was updated successfully, but these errors were encountered: