Re: [Puppet Users] PC EU feedback: virtual resource operator is too magical, hard to read
Jordan Sissel:
+1 to this. Any change here should also updae the export syntax as well.
replace @@user { foo: ; }
with export user { foo: ; }
Agreed!
Any plans on making the realizing/importing queries changed as well?
realize/query: User | title == foo |
export query: User | title == foo |
Perhaps a server-side function, like collect_exports(Resource,
expression) or perhaps extend the Realize directive to support
expression matching somehow.
However it's done, I agree that the query syntax should be made explicit
at the same time as export.
--
On my TV show, when I say and where do we put policy?
the audience will yell USERSPACE! -- Sean Q. Neakums
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] PC EU feedback: virtual resource operator is too magical, hard to read
On Fri, May 20, 2011 at 3:15 PM, Jordan Sissel j...@semicomplete.com wrote:
On Fri, May 20, 2011 at 1:20 PM, Randall Hansen rand...@puppetlabs.comwrote:
http://projects.puppetlabs.com/issues/7605
The virtual resource operator:
@user { luke: ensure = present }
Is relatively easy to type but, if you don’t know it, very hard to
read. We should consider a word-based syntax, e.g.:
virtual user { luke: ensure = present }
Please comment on the ticket or reply here, whichever you prefer.
Thanks!
r
+1 to this. Any change here should also updae the export syntax as well.
replace @@user { foo: ; }
with export user { foo: ; }
+1
Any plans on making the realizing/importing queries changed as well?
realize/query: User | title == foo |
export query: User | title == foo |
-Jordan
P.S. This is in response to feedback from my Improving the Puppet
DSL session at Puppet Camp EU, 2011. This ticket isn't a promise we
will take action, but we could very much like comment and discussion
from you good people.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] PC EU feedback: virtual resource operator is too magical, hard to read
http://projects.puppetlabs.com/issues/7605
The virtual resource operator:
@user { luke: ensure = present }
Is relatively easy to type but, if you don’t know it, very hard to
read. We should consider a word-based syntax, e.g.:
virtual user { luke: ensure = present }
Please comment on the ticket or reply here, whichever you prefer.
Thanks!
r
P.S. This is in response to feedback from my Improving the Puppet
DSL session at Puppet Camp EU, 2011. This ticket isn't a promise we
will take action, but we could very much like comment and discussion
from you good people.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] PC EU feedback: virtual resource operator is too magical, hard to read
On Fri, May 20, 2011 at 1:20 PM, Randall Hansen rand...@puppetlabs.comwrote:
http://projects.puppetlabs.com/issues/7605
The virtual resource operator:
@user { luke: ensure = present }
Is relatively easy to type but, if you don’t know it, very hard to
read. We should consider a word-based syntax, e.g.:
virtual user { luke: ensure = present }
Please comment on the ticket or reply here, whichever you prefer.
Thanks!
r
+1 to this. Any change here should also updae the export syntax as well.
replace @@user { foo: ; }
with export user { foo: ; }
Any plans on making the realizing/importing queries changed as well?
realize/query: User | title == foo |
export query: User | title == foo |
-Jordan
P.S. This is in response to feedback from my Improving the Puppet
DSL session at Puppet Camp EU, 2011. This ticket isn't a promise we
will take action, but we could very much like comment and discussion
from you good people.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
