[PUP-9144] PAL for Catalog Compilation does not evaluate defines and classes Created: 2018/09/17  Updated: 2018/10/02  Resolved: 2018/09/26

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: PUP 6.0.1

Type: Bug Priority: Major
Reporter: Henrik Lindberg Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template: PUP Bug Template
Acceptance Criteria:

That all declared classes and resources are included in the catalog the same way in a regular compilation.

Epic Link: 6.y PAL API
Team: Platform Core
Method Found: Needs Assessment
Release Notes: Not Needed
Release Notes Summary: PAL is not really released to the public.
QA Risk Assessment: Needs Assessment

 Description   

The PAL support for catalog compilation does not evaluate defines and classes if they are defined inside of the body of the PAL. Thus a catalog will only instances of classes and resources that were evaluated during the main part of the compilation (i.e. if given a manifest or initial code to evaluate). Three new methods were added to the API to control lazy evaluation and validation of the result.



 Comments   
Comment by Eric Thompson [ 2018/09/20 ]

Henrik Lindberg does this need to land in 6.0.1. if so, do you have people who can review it?

Comment by Henrik Lindberg [ 2018/09/20 ]

Eric Thompson Yes, it is used in Bolt - I think Lucy Wyman is already trying out the PR. I am working on tests for that PR.

Comment by Josh Cooper [ 2018/09/26 ]

Passed CI in e2f7ccfb7

Generated at Fri Oct 18 01:33:07 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.