Jira (PUP-7531) give user control over optional/strict in hiera interpolation

2017-10-25 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-7531 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: give user control over optional/strict in hiera interpolation   
 
 
 
 
 
 
 
 
 
 
Ping Eric Sorenson - this needs product / Ux love - should we help with the problems described and work on the suggested solution? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7531) give user control over optional/strict in hiera interpolation

2017-06-01 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7531 
 
 
 
  give user control over optional/strict in hiera interpolation   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 PUP-7530 deals with the uniqueness of input in a hiera.yaml. That issues is a problem in general, but was detected for the special case of {{undef}} in the input.Currently the user has no way to declare that interpolated values must exist. If {{\--strict_variables}} is turned on an operation will fail when referencing a non existing variable, but there is nothing indicating if a value is missing in a navigation (unless trying to navigate passed an {{undef}}).The following could be a solution:* if an interpolation is followed by {{=}}, the remainder up to the closing of the interpolation is taken as the default value to use for that interpolation if the left of the {{=}} resulted in {{undef}}, either because variable is not set, or if navigation into value produces {{undef}}.* if an interpolation is followed by {{!}}, the reference is taken as a strict reference. ** In a hiera.yaml interpolation this is taken as a disqualification of the input (the path is skipped). This is of value as it saves the user from inventing paths to files like 'nothing' (with the risk of someone putting something in that file), or using a directory path as a path to 'nothing' (which is harder to understand). When skipped explain contains this information. No warning is issued as user asked for this processing to take place.** In interpolation of a data value, this would result in explain output and a warning * It is not possible to combine {{=}} and {{!}} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
  

Jira (PUP-7531) give user control over optional/strict in hiera interpolation

2017-05-17 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7531 
 
 
 
  give user control over optional/strict in hiera interpolation   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Labels:
 
 triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7531) give user control over optional/strict in hiera interpolation

2017-05-17 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7531 
 
 
 
  give user control over optional/strict in hiera interpolation   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Team:
 
 Agent 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7531) give user control over optional/strict in hiera interpolation

2017-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7531 
 
 
 
  give user control over optional/strict in hiera interpolation   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/05/15 2:51 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
PUP-7530 deals with the uniqueness of input in a hiera.yaml. That issues is a problem in general, but was detected for the special case of undef in the input. 
Currently the user has no way to declare that interpolated values must exist. If --strict_variables is turned on an operation will fail when referencing a non existing variable, but there is nothing indicating if a value is missing in a navigation (unless trying to navigate passed an undef). 
The following could be a solution: 
 

if an interpolation is followed by =, the remainder up to the closing of the interpolation is taken as the default value to use for that interpolation if the left of the = resulted in undef, either because variable is not set, or if navigation into value produces undef.
 

if an interpolation is followed by !, the reference is taken as a strict reference. 
 

In a hiera.yaml interpolation this is taken as a disqualification of the input (the path is skipped). This is of value as it saves the user from inventing paths to files like 'nothing' (with the risk of someone putting something in that file), or using a directory path as a path to 'nothing' (which is harder to understand). When skipped explain contains this