Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(PUP-5075) Check that types that produces caps can use qualified names #4195

Merged

Conversation

thallgren
Copy link
Contributor

This commit adds a test that verifies that a resource type that
consumes/produces capabilities may have a qualified name.

This PR sits on top of #4183. The PUP-5075 commit is the only one to consider here.

This commit ensures that the resolution of declared capability
mappings is deferred until all files for a particular environment
has been parsed.

The commit introduces a new Resource::Type named 'capability_mapping'
that acts as intermediate object created by the parser and added to a
hash in the known_resource_types TypeCollection which is later made
available to the compiler. The compiler uses these objects when it's
time to evaluate to perform the actual mapping between capabilities
and resources. Once the mapping is complete, the 'capability_mapping'
hash is no longer needed and is cleared out to conserve memory.
This commit adds a test that verifies that a resource type that
consumes/produces capabilities may have a qualified name.
hlindberg added a commit that referenced this pull request Aug 28, 2015
…nd-qnames

(PUP-5075) Check that types that produces caps can use qualified names
@hlindberg hlindberg merged commit b192647 into puppetlabs:master Aug 28, 2015
@thallgren thallgren deleted the issue/pup-5075/capabilities-and-qnames branch December 16, 2015 07:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants