Jira (PUP-9186) Deferred doesn't work in 'notify' resource

Henrik Lindberg (JIRA) Fri, 28 Sep 2018 01:26:50 -0700

Title: Message Title

You cannot do something like this:

notify { "hello ${Deferred('pid', [])}": }

and expect that to have a title that is resolved on the agent - that is the id of the notify - it must be known when compiling.

You can also not do this:

notify { "test": message => "hello ${Deferred('pid', [])}" }

And expect that the entire message string is resolved and then formatted on the agent side. To be clear why this is the case; consider the semantics of string interpolation: "evaluate an _expression_, transform to string, and concatenate" - thus, when an instance of Deferred is interpolated it will naturally be transformed to its string form.

Thus, a Deferred inside of interpolation, (or inside an EPP template for that matter) will not mean that the string/template is resolved on the agent side.

You can do like in this example to make it work:

notify { "test": message => Deferred('sprintf', [ 'hello %d', Deferred('pid', [])]) }

or, use EPP:

notify { "test": message => Deferred('inline_epp', [ 'hello <%= pid([]) %> ' ]) }

That works because the wanted result is a string - for something that should return something that is not a string, the approach above must be used.

Agree this should be pointed out - it will probably be a common thing that people wonder how to do.

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 (PUP-9186) Deferred doesn't work in 'notify' resource

Reply via email to