[no description] https://git.osdyson.ru/pkg-puppet/puppet/atom?h=master 2014-07-08T21:59:55Z 2014-07-08T21:59:55Z Andrew Parker andy@puppetlabs.com 2014-07-08T21:59:55Z urn:sha1:590a9ab00ed81bc140732e1bced60e160ca48b31 * pr/2819: (maint) Remove biff setting and related code (PUP-2858) Remove evaluator setting (PUP-2858) Remove duplicated testing (evaluator = 'current') (PUP-2858) Refactor binder to use ne evaluator (PUP-2858) Remove the 3_1 checker and its factory (PUP-2858) Refactor EvaluatingParser::Transitional to EvaluatingParser (PUP-2858) Remove use of Puppet[:evaluator] from the code base (PUP-2858) Deprecate the use of Puppet[:environment] == current (PUP-2858) Remove e_parser adapter support Conflicts: spec/integration/node/environment_spec.rb Closes #2819 2014-07-04T23:15:44Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-07-03T00:10:39Z urn:sha1:4e508533814142163821c9286ae3f5c68dd0b3aa This makes the ability to load all .pp files under a manifest dir recursively conditional to parser == future. (It will become the standard in Puppet 4.0). This is done to avoid slurping in lots of files in case users kept other files around in a subdirectory in the belief that they would not be loaded. Thus making it harder to upgrade. This also adds a test that runs for future parser. 2014-07-03T21:14:20Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-07-03T21:14:20Z urn:sha1:1d218c0e25ecb0fb45d3df9c1ac9b15d08a35887 There was a test (environment_spec) that ran an extra time with the hybrid parser = future, evaluator = current which results in the same tests running twice. (This because the future evaluator is enforced when runing with future parser). 2014-04-27T19:15:43Z Andrew Parker andy@puppetlabs.com 2014-04-27T19:15:43Z urn:sha1:f035381a1c0107b60ebec7669645b1fb469b5f9b Using the have_resource matcher makes the tests a little shorter and more expressive. It also uses the common way of matching so that we can get better error reporting. It turns out that one of the tests was matching against the incorrect class name, so that is now fixed. This also extracts a be_resource matcher so that you can match against an individual resource independent of a catalog. 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-02-03T23:30:11Z Andrew Parker andy@puppetlabs.com 2014-02-03T23:25:45Z urn:sha1:4d408df0de3ac100eedd83f304f3697b03d8a315 2014-02-03T23:30:05Z Andrew Parker andy@puppetlabs.com 2014-02-03T23:18:09Z urn:sha1:dae56db2a224610ad4af76067185eb4e30b1a5c6 The future evaluator is only really in play when both the parser is future and the evaluator is future. The old check left out the evaluator portion of that check and so ended up using the wrong CodeMerger when using the current evaluator with the future parser. 2014-02-03T23:29:55Z Andrew Parker andy@puppetlabs.com 2014-02-03T22:27:49Z urn:sha1:83c0eff03996e5003f8386c816515f1651729246 Previously BlockExpression would skip evaluating any AST nodes that implement an instantiate method. The assumption was that instiate only existed on Hostclass, Node, and Definition AST nodes and those same classes also did not implement an evaluate method. With the introduction of the PopsBridge::Program class, this entire house of assumption cards came falling down, since it impelements both instantiate and evaluate. The only thing that truly prevented BlockExpression from calling evaluate was that the default evaluate implementation on Parser::AST raised a Puppet::DevError to try to catch the case of evaluate not being implemented for an AST class. Since Parser::AST is entirely internal and missing an evaluate should show up very quickly in tests, we can just as easily make evaluate a noop by default, which then simplifies BlockExpression. This change fixes the problem where the body of pp files were loaded, but not evaluated when using the future evaluator and a directory of manifest files. The problem was triggered by the BlockExpression logic interacting with the PopsBridge::Program object and the structure created by the Puppet::Pops::Parser::CodeMerger. 2014-01-29T18:29:20Z Andrew Parker andy@puppetlabs.com 2014-01-27T22:23:20Z urn:sha1:5c988b988840eddd4081c60f48e924dffe56d6d7 Instead of creating environments directly, we need to go through the configured environment loaders, otherwise environments can't come from other places. 2014-01-06T18:04:17Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-01-03T00:39:51Z urn:sha1:938b4e7d495f5f15557110040458171e832cecf2 This changes the API in a new implementation in a file called file_.rb The intent is that it should replace the implemntation in File, or perhaps directly in a Puppet::FileSystem class.