Jira (PUP-3636) Converting from config environments should be less confusing

[Moses Mendoza (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3636 
 
 
 
  Converting from config environments should be less confusing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Labels:
 
 triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3636) Converting from config environments should be less confusing

[Luke Kanies (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Luke Kanies created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3636 
 
 
 
  Converting from config environments should be less confusing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Created:
 

 2014/11/06 8:20 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Luke Kanies 
 
 
 
 
 
 
 
 
 
 
Trying to follow the path of deprecation warnings from a puppet.conf that specifies modulepath and manifest to one that uses directory environments is quite confusing. 
The link given by the warning: http://links.puppetlabs.com/env-settings-deprecations 
points to the old configuration instead of a page about how to convert. Yes, that page has deprecation warnings, but this doesn't make sense. The link should point to the new configuration, with some migration information. 
Then, when you follow the link to the new page, it doesn't talk about the actual parameters you have to convert. The page is here: 
https://docs.puppetlabs.com/puppet/latest/reference/environments.html 
And there's no mention at all of 'manifest' or 'modulepath' on this page. 
These deprecation warnings need a clear path of migration - not a link to more detail on the deprecation, but a link to detail on how to make the warning go away. If I'm using 'manifest' and 'modulepath' to override these values right now (which I am, in my home directory, when running Puppet as myself on my laptop), how do I convert to directory environments? Note that I'm not actually using environments at all, I just want a custom value for these variables. 
How do I make these warnings go away? Where is that clearly documented?