Jira (BOLT-1085) Optional data type, null and bash

Brett Gray (JIRA) Thu, 10 Jan 2019 15:11:08 -0800

Title: Message Title

Brett Gray created an issue

Issue Type:	Improvement
Assignee:	Unassigned
Created:	2019/01/10 3:10 PM
Priority:	Normal
Reporter:	Brett Gray

If I have a plan as follows:

plan mongodb::sub_test (

  TargetSpec          $nodes,

  String              $a,

  String              $b,

  Optional[String[1]] $c = undef,

) {

  $return_hash = run_task('beergeek::test', $test_data['nodes'], a => $a, b => $b, c => $c)

and this Bash Task:

#!/bin/sh

a=$PT_a

b=$PT_b

c=$PT_c

mkdir -p /tmp/{${a},${b},${c}}

echo `ls -l /tmp`

If I provide a JSON params file as follows:

      "nodes": ["x.x.x.x."],

      "a": "a",

      "b": "b"

My result will be:

[ec2-user@ip-x-x-x-x ~]$ ls /tmp/

a  b  null

Bolt appears to parse the value null when no value is provided for any Optional data type when using Bash (I have not tested other languages). This requires the developer to include further validation of input. Can you please confirm if this is by design and if it is can you please provide documentation on this functionality?

Add Comment

This message was sent by Atlassian JIRA

--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1085) Optional data type, null and bash

Reply via email to