There is no reason to allow alternate environments or alternative pat…

…hs. If someone can prevent a good use case, I will add it back, but I don't see any situations in which there isn't a simple workaround

README.md

@@ -15,10 +15,10 @@ can Puppetize the setup of the Puppet server in your new environment by installi
 modules from a given list.
 
 This module can also ensure that all of your modules are at the latest versions by installing
-updates. While Code Manager or r10k can do this and much more, Code Manager requires a Puppet 
-Enterprise licese and r10k setup and management is extremely complicated. This is a much simpler
-system and can be thought of at Code Manager/r10k lite. It is perfect for those who are not coding
-much more than a basic module and are using mostly off-the-shelf Puppet Forge modules.
+updates. While Code Manager or r10k can do this and much more, Code Manager requires a Puppet
+Enterprise licese and r10k setup and management is extremely complicated. This is a much simpler 
+system and can be thought of at Code Manager/r10k lite. It is perfect for those who are not 
+coding much more than a basic module and are using mostly off-the-shelf Puppet Forge modules.
 
 ## Setup
 
@@ -45,17 +45,14 @@ class
 In the above example, if a module is not detected, the latest version will be installed. If it is
 if it is already installed, then modman will check for updates. 
 
-However, you may find that you need to install to a non-default environment or directory,
-need to pin to a specific version of a module, that you want to intall updates only during a 
-specified maintenance window, and/or that you have dependancy conflicts and you need to ignore
-dependancies. If you need all of these, then the most complicated usage of modman would be:
+However, you may find that you need need to pin to a specific version of a module and/or that you 
+have dependancy conflicts and you need to ignore dependancies. If you need all of these, then the
+most complicated usage of modman would be:
 
 ```
 class
 {
         'modman':
-                target_dir 	=> "/etc/puppet/environment/test"
-                environment	=> "QA"
                 modules 	=> [
                         { name  => "puppetlabs-stdlib", version => "4.10" },  #try_get_value deprecated in version 4.12, but we require it
                         { name	=> "puppetlabs-firewall" },
@@ -73,8 +70,4 @@ or have an issue to file, you may do so there.
 
 ## Release Notes
 
- * Test version pinning
- * Test ignoring dependancies
- * Test non-default env
- * Test non-default target dir
  * We are planning to allow you to supply a cron-style time to the class to allow you to schedule the updates for a specific maintenance window

manifests/init.pp

@@ -18,8 +18,6 @@
 # class
 # {
 #   'modman':
-#      target_dir      => "/etc/puppet/environment/test"
-#      environment     => "QA"
 #      modules         => [
 #              { name  => "puppetlabs-stdlib", version => "4.10" },  #try_get_value deprecated in version 4.12, but we require it
 #              { name  => "puppetlabs-firewall" },
@@ -62,8 +60,6 @@
 #
 
 class modman (
-	$target_dir = undef,
-	$environment = undef,
 	$modules = []
 ){
 	each($modules) |$module|