[no description] https://git.osdyson.ru/pkg-puppet/puppet/atom?h=master 2014-08-29T21:53:36Z 2014-08-29T21:53:36Z Josh Partlow joshua.partlow@puppetlabs.com 2014-08-29T21:53:36Z urn:sha1:4f67f7b93a1c7517240d8a9948a5107a2a424723 After discussion with Nick Fagerlund and Henrik Lindberg, changing restrict_environment_manifest setting to disable_per_environment_manifest to more clearly reflect what the setting does. 2014-08-29T18:33:21Z Josh Partlow joshua.partlow@puppetlabs.com 2014-08-28T22:41:14Z urn:sha1:acf6f9b4a6b1489f9b1e5d7d85a236324e53470c Henrik brought up that with the new restrict_environment_manifest setting set true, authors of modules in a particular environment may be surprised by a manifest they have specified in their environment.conf not being pulled in, leading to bad behavior when a catalog is executed. Although this is logged on the master, compilation delivery and catalog execution is not prevented. This commit will raise an exception on the master prior to catalog compilation if it detect's a conflict between manifest settings in the requested environment. 2014-05-30T20:22:29Z Andrew Parker andy@puppetlabs.com 2014-05-30T20:22:29Z urn:sha1:51ef1733696ea3f661d2ce7d260f2ea651a0203f This fixes environment equality to make it work as a hash key. It also adds tests around this functionality. 2014-04-21T21:03:50Z Pieter van de Bruggen pvande@gmail.com 2014-04-21T21:03:50Z urn:sha1:2c2608b27d3031b86b419b946e78883cc4b5c597 Conflicts: spec/unit/face/module/install_spec.rb spec/unit/face/module/list_spec.rb spec/unit/face/module/uninstall_spec.rb spec/unit/module_tool/applications/installer_spec.rb spec/unit/module_tool/applications/uninstaller_spec.rb spec/unit/module_tool_spec.rb 2014-04-09T14:08:14Z Andrew Parker andy@puppetlabs.com 2014-04-09T14:08:14Z urn:sha1:6540ec01f8404fc916bed0dbd918bdbe291a475e * upstream/stable: (PUP-2158) Unlist configured environment (PUP-2158) Test dynamic environments with an empty environmentpath (PUP-2158) Fix integration apply application spec (PUP-2129) Fix issues with false interpolation start (no-such-method) (PUP-2158) Report 404 for missing environment (PUP-2158) Default a missing manifest to no_manifest (PUP-2158) Hide dir envs behind a feature flag Conflicts: lib/puppet/node/environment.rb spec/unit/environments_spec.rb 2014-04-07T18:22:29Z Pieter van de Bruggen pvande@gmail.com 2014-04-07T18:22:29Z urn:sha1:4f255ffbdbbdc413c38b9c4130c17fdc285b7163 In master, hyphenated module names are supported (effectively) everywhere except as the name of a dependency. A previous commit in this branch attempted to alleviate that situation, but failed to adequately test the change and its implications, and potential failures existed. This change introduces a change to existing tests that triggers the offensive behavior both in master and in this branch, and refactors the implementation to apply the necessary transliteration in all required locations. 2014-04-07T15:01:38Z Andrew Parker andy@puppetlabs.com 2014-04-07T15:01:38Z urn:sha1:f6637b0a3dba8bed9cd039ff22e644ea38040a84 The tests were often creating environments that didn't need to have manifests. Since we didn't have a way of specifying that when they were written, we used '' to fill in the blank. This actually caused a large number of tests to try to find code to load in the PWD, which caused tests to break if a developer had parse errors in manifests being used for testing in the root directory of their puppet project. This changes the manifest to be optional and removes '' from those tests. The tests no longer fail if a bad manifest is in the PWD :D 2014-03-21T15:46:10Z Josh Partlow joshua.partlow@puppetlabs.com 2014-03-20T20:13:30Z urn:sha1:ea9f5edb4478472bd3ca8c9c12a6265712ecdbb3 When reading EnvironmentConf settings, relative paths were prepended with the directory environment path. This commit ensures that we also expand the paths properly so that they are absolute on both Windows and Posix platforms. 2014-03-19T00:21:56Z Josh Partlow joshua.partlow@puppetlabs.com 2014-03-07T23:02:55Z urn:sha1:1221f59e2ed4724116df69b47341fc9634440440 Legacy environments could have config_version set in their puppet.conf stanza, just as any setting in an [env] stanza would shadow if that setting was looked up in the context of the environment. But the new directory environments are intended to explicitly include config_version as a setting (albeit an optional one). This change adds a config_version attribute to Puppet::Node::Environment, looking it up from settings if a new call is made, or taking it directly from a create call, which is what the Directory environments loader will do once environment.conf is parsed for directory environments. 2014-02-22T11:25:29Z Dominic Cleal dcleal@redhat.com 2014-02-21T20:22:17Z urn:sha1:b5b96cf8fc5286882077966f6e6448f2ae7ed6d9 Puppet::Node::Environment.current is used in some external code, so reimplement it, linking to the context lookup for the current environment and issue a deprecation warning.