-
Notifications
You must be signed in to change notification settings - Fork 51
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 option to inform about deprecated modules #148
Comments
Which g10k version are you using or are you using g10k with g10k has this since v.0.4.8 (https://github.com/xorpaul/g10k/releases/tag/v0.4.8), but doesn't report it when using
Otherwise if g10k fails to detect this please post an example Puppetfile for me to debug. |
Puppetfile:
g10k
r10k 3.3.1
|
Ah, when you specify a version g10k would try to load this out of it's cache without contacting the Puppetlabs Forge in any way. Seems like r10k did always query the Forge API and not use a cache like g10k did. With v0.7.4 I've added this query to check for deprecation notices. If you're using many Puppetlabs Forge modules in your Puppetfile I suggest specifying a cache for that metadata/deprecation information query by adding
or something similar to your Puppetfile(s). |
r10k gives you warnings like that
it would be nice to have this also in g10k.
The text was updated successfully, but these errors were encountered: