fixes #2878 - Import Classes fails when using parser = future #123
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[Test] |
| end | ||
|
|
||
| end | ||
| end | ||
| end |
There was a problem hiding this comment.
Nitpick, but I'd keep the line ending here.
|
[test] |
This code is only valid for Puppet >= 3.2
|
This is awesome, thanks for the contribution @rickard-von-essen. I fixed a couple of weird issues under Ruby 1.8.7 and Puppet 3.2+, but all merged into af58b9f for Foreman 1.4. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables smart-proxy to read puppet classes which contains new lambda constructs when
parser = futureoption is used.For more information see:
http://docs.puppetlabs.com/puppet/3/reference/experiments_future.html
http://projects.theforeman.org/issues/2878