puppet.git/test/data/snippets, branch ticket/master/7841

Fix #2389 - Enhance Puppet DSL with Hashes

2010-02-17T14:50:53+00:00

This bring a new container syntax to the Puppet DSL: hashes.

Hashes are defined like Ruby Hash:
{ key1 => val1, ... }

Hash keys are strings, but hash values can be any possible right
values admitted in Puppet DSL (ie function call, variables access...)

Currently it is possible:

1) to assign hashes to variable
$myhash = { key1 => "myval", key2 => $b }

2) to access hash members (recursively) from a variable containing
a hash (works for array too):

$myhash = { key => { subkey => "b" }}
notice($myhash[key][subjey]]

3) to use hash member access as resource title

4) to use hash in default definition parameter or resource parameter if
the type supports it (known for the moment).

It is not possible to string interpolate an hash access. If it proves
to be an issue it can be added or work-arounded with a string concatenation
operator easily.

It is not possible to use an hash as a resource title. This might be
possible once we support compound resource title.

Unlike the proposed syntax in the ticket it is not possible to assign
individual hash member (mostly to respect write once nature of variable
in puppet).

Signed-off-by: Brice Figureau

Enhance selector and case statements to match with regexp

2009-08-01T01:15:29+00:00

The case and selector statements define ephemeral vars, like 'if'.

Usage:

case statement:
$var = "foobar"
case $var {
    "foo": {
         notify { "got a foo": }
    }
    /(.*)bar$/: {
         notify{ "hey we got a $1": }
    }
}

and for selector:
$val = $test ? {
  /^match.*$/ => "matched",
  default => "default"
}

Signed-off-by: Brice Figureau

Fix #2033 - Allow regexp in if expression

2009-08-01T01:15:29+00:00

This changeset introduces regexp in if expression with the use of the
=~ (match) and !~ (not match) operator.

Usage:

if $uname =~ /Linux|Debian/ {
  ...
}

Moreover this patch creates ephemeral variables ($0 to $9) in the current
scope which contains the regex captures:
if $uname =~ /(Linux|Debian)/ {
  notice("this is a $1 system")
}

Signed-off-by: Brice Figureau

Fix #2333 - Make sure lexer skip whitespace on non-token

2009-06-12T12:52:29+00:00

Comments and multi-line comments produces no token per-se during
lexing, so the lexer loops to find another token.
The issue was that we were not skipping whitespace after finding
such non-token.

Signed-off-by: Brice Figureau

Removed extra whitespace from end of lines

2009-06-05T23:12:00+00:00

Changed tabs to spaces without interfering with indentation or alignment

2009-06-05T23:11:28+00:00

Fix #1088 - part2 - Add rspec tests

2009-03-14T00:31:29+00:00

Signed-off-by: Brice Figureau

Fix #1402 - Allow multiline comments

2008-10-29T09:30:38+00:00

Signed-off-by: Brice Figureau

Fix #857 - Multiple class of the same name don't append code

2008-10-29T09:28:32+00:00

The following manifest wasn't working:
class one {
notice('class one')
}

class one {
notice('second class one')
}

include one

It all boiled down to class code not being arrays.
Encapsulating code in ASTArray when needed is enough to append code,
because of the property of ASTArray to evaluate all their members in
turn.

Signed-off-by: Brice Figureau

Fix #936 - Allow trailing comma in array definition

2008-10-21T10:15:53+00:00

Signed-off-by: Brice Figureau