Issue #14301 has been updated by Andrew Parker.

Status changed from Accepted to Ready for Documentation
Assignee changed from Andrew Parker to Charlie Sharpsteen

I'm a little reluctant to try and manipulate the parser again, since there seem 
to be a lot of interdependencies and corner cases that are hard for us to see. 
I think that this is something that is be fixed when the "future" parser (for 
the iteration work") becomes the default parser and not before.

That puts the fix for this on a major release timeline. At the moment it is 
looking like it will be a 4.0 release, but I don't know the timeframe.

----------------------------------------
Bug #14301: Hashes can not be used in selectors (upgrading from 2.7.1->2.7.14)
https://projects.puppetlabs.com/issues/14301#change-90984

* Author: Kristian Kostecky
* Status: Ready for Documentation
* Priority: Normal
* Assignee: Charlie Sharpsteen
* Category: parser
* Target version: 
* Affected Puppet version: 2.7.14
* Keywords: selector hash_literal customer
* Branch: 
----------------------------------------
After upgrading from puppet 2.7.1 -> 2.7.14, I noticed that all the selectors 
that assigned hashes caused a parse error. I re-wrote them as if conditionals 
to bypass the issue, but I believe this is a bug.

Example:

  $test = $fqdn ? {
    'test'  => { 'test' => 'test', 't' => 't' },
    default => { 'test' => 'test', 't' => 't' },
  }

Gives:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could 
not parse for environment production: Syntax error at '{'; expected '}' at 
XXXXXX


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to