Add Pyobjects (formerly NaCl) to Salt

[borgstrom]

This adds a new renderer #!pyobjects that provides an object based interface for building state data.

See the following for more background:

• https://groups.google.com/forum/#!topic/salt-users/5frdabVwAdE
• https://github.com/borgstrom/nacl
• http://borgstrom.ca/2014/02/15/building-a-pythonic-interface-to-saltstack-states.html

[ghost]

Test FAILed.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/1560/

[whiteinge]

Nice!

[s0undt3ch]

Can you please switch to:

log = logging.getLogger(__name__)

[borgstrom]

Right, I switched to "pyobjects" during testing to ensure I was getting log messages at one point. This has been switched back to name.

[s0undt3ch]

Awesome!

[s0undt3ch]

Aside from my comment(minor change), I think this is awesome!

[ghost]

Test FAILed.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/1565/

[ghost]

Test FAILed.
Refer to this link for build results: http://jenkins.saltstack.com/job/salt-pr-build/1566/

[thatch45]

I really like this! Thanks @borgstrom! I am wondering if this works with the top file, and if not if it could be extended to do so.

@basepi, we can cherry this into 2014.1

[borgstrom]

Thanks! Is there anything else you'd recommend I do from a documentation
standpoint?
On Feb 18, 2014 1:13 PM, "Thomas S Hatch" [email protected] wrote:

I really like this! Thanks @borgstrom https://github.com/borgstrom! I
am wondering if this works with the top file, and if not if it could be
extended to do so.

@basepi https://github.com/basepi, we can cherry this into 2014.1

Reply to this email directly or view it on GitHubhttps://github.com//pull/10517#issuecomment-35414787
.

[erchn]

Are there any docs on how salt modules would be called, or how to reference pillar data? if it's like a normal #!py that's fine, though it seems less than ideal given how nicely states are presented.

Sorry if this is too obvious, but I'm unclear how includes would work as well.

[borgstrom]

@erchn currently you access salt & pillar the same way as the other renderers, through the default objects that Salt provides (ie. salt['cmd.run'](bar)). However, I did just submit a pull request (#10600) to add an object interface to Salt (Salt.cmd.run(bar)). I supposed adding a Pillar object that provides a simple proxy to the pillar.get Salt function might be a nice touch, (ie. salt['pillar.get']('foo:bar:baz', 'qux') and Pillar('foo:bar:baz', 'qux') would be functionally equivalent)

Includes & Extends are documented in the renderer (https://github.com/saltstack/salt/blob/develop/salt/renderers/pyobjects.py#L91)