[PUP-7674] Resource collectors fails to load generated resource types. - Puppet Tickets

XML

Word

Printable

Template:
customfield_10700 196739
Acceptance Criteria:

Hide

That resource collectors (both normal and exported), when used during compile, only loads resources generated by puppet generate types when such resources exists.

Show
That resource collectors (both normal and exported), when used during compile, only loads resources generated by puppet generate types when such resources exists.
Sub-team:
- Language
Team:
Agent
Story Points:
1
Sprint:
Agent 2017-06-28
Method Found:
Customer Feedback

Release Notes:
Bug Fix
Release Notes Summary:

Hide
A problem was found with the environment isolation solution ({{generate types}} where a collection of a type would cause it to be loaded as a Ruby implementation instead of the generated meta data. This in turn could cause isolation problems if different environments had different versions of this type.
This is now fixed so collectors also load the generated meta data form if present.

Show
A problem was found with the environment isolation solution ({{generate types}} where a collection of a type would cause it to be loaded as a Ruby implementation instead of the generated meta data. This in turn could cause isolation problems if different environments had different versions of this type. This is now fixed so collectors also load the generated meta data form if present.

A resource collector will always load the ruby resource, even if resources has been generated using puppet generate types.

blocks

PUP-7657 Providers requiring files in other modules might cause intermittent compilation failures

relates to

PUP-7683 acceptance: add test ensuring that generated types take presedence over ruby types