RubyMine 2017.1.2 EAP: Improved Detection of Puppet Modules, Fixed Issues

Hi there,

We have updated the stable version to RubyMine 2017.1.1. and we recommend updating to it as it fixes the painful RSpec regression, performance issues, and other bugs. Read more there.

We are working on the next version and in this post we’d like to announce RubyMine 2017.1.2 EAP (build 171.4249.6) which brings the following improvements:

Puppet improvements

This EAP build should fix the issues with the resolution of Puppet modules which surfaced after updating to v2017.1 and made users downgrade:

Now RubyMine can read modulepath from environment.conf. E.g., if you have site and modules subdirectories and you specify modulepath = site:modules in environment.conf, the IDE will detect the modules in the site and modules subdirectories:

Modulepath Puppet RubyMine

To make this work, you need to have environment.conf inside the project you are currently working on, otherwise RubyMine won’t be able to detect it.

Also, the IDE now can detect modules in dependencies directories without the need for metadata.json, as requested by our users. For example, if your environment contains environment.conf or Puppetfile, then all subdirs inside the /modules/ directory will be treated as modules regardless of metadata.json. RubyMine will also catch the dependencies of those modules.

Fixed issues

We’ve also fixed the following issues in this update:

See the release notes for the full list of improvements.

Download this EAP and use our tracker to report any issues you face.

Cheers!

Your RubyMine Team

This entry was posted in Announcement, WhatsMining and tagged , , . Bookmark the permalink.

2 Responses to RubyMine 2017.1.2 EAP: Improved Detection of Puppet Modules, Fixed Issues

  1. Erik Swanson says:

    I’m curious what scenario “… RubyMine will also catch the dependencies of those modules.” was tested under, given that dependency resolution among metadata.json-free modules most definitely does not work. See RUBY-19476

    2017.x is still totally unusable for Puppet. :(

Leave a Reply

Your email address will not be published. Required fields are marked *