Re: [Puppet Users] PC EU feedback: unpack array variables in string interpolation
What should this do?
$array = [ "one", "two" ]
$greeting = [ "hello", "howdy" ]
@file { "host_$array$greeting" }
or this?
$array = [ "one", "two" ]
@file { "$array_blah" }
seems like we would need delimiters
"host_${array}_${greeting}"
and some form of expansion control.
Should it expand zipper-wise or combinatorially?
Probably all of that belongs in functions,
not in the resource or string syntax.
--
vagn
On 05/20/2011 04:15 PM, Randall Hansen wrote:
http://projects.puppetlabs.com/issues/7598
If your goal is this (pseudo-code):
@file { "host_one" }
@file { "host_two" }
You should be able to say this:
$array = [ "one", "two" ]
@file { "host_$array" }
Instead of this:
@file { "host_one", "host_two" }
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: exported resource syntax is too magical, hard to read
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If you really want to simplify people's life, make those extra
> attributes become metaparameters (but please keep the old syntax):
>
> user { luke: ensure => present, virtual => [boolean] }
>
> That would even allow us to parametrize virtuality/exportability with
> the help of an expression (ie selectors, functions, boolean expressions ...)
awesome!
+1
~pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3cM2YACgkQbwltcAfKi38nlACfQZ7M5Lc9UoLruDr99VmEG21o
vKAAoIeR39sgLeQO90Uu5qGRyVpWFyhc
=nJQx
-END PGP SIGNATURE-
--
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: exported resource syntax is too magical, hard to read
Nigel Kersten:
> On Sat, May 21, 2011 at 1:42 AM, Brice Figureau <
> brice-pup...@daysofwonder.com> wrote:
> > If you really want to simplify people's life, make those extra
> > attributes become metaparameters (but please keep the old syntax):
> >
> > user { luke: ensure => present, virtual => [boolean] }
> >
> > That would even allow us to parametrize virtuality/exportability with
> > the help of an expression (ie selectors, functions, boolean expressions
> > ...)
> ++
>
> This would be great. Being able to filter on virtual/export status would be
> killer.
Oh yes indeed! I can already think of ways to use this.
--
"Man, if everything were object-oriented then rsync
could do this already. Of course, if everything were
object-oriented I'd have a bushy moustache and be
wearing flares, which would suck." -- Sean 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: spaceship operator too magical, hard to read
Nan Liu: > On this subject, should we support regular expression? > User <| title =~ /*adm/ |> If you're going down this road, it's probably worthwhile to add the full set of comparison operators such as <= and so forth. -- "There should be a homonym exam before people are issued keyboards." -- George Moffitt -- 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
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: exported resource syntax is too magical, hard to read
On 5/21/11 10:42 AM, Brice Figureau wrote:
If you really want to simplify people's life, make those extra
attributes become metaparameters :
user { luke: ensure => present, virtual => [boolean] }
That would even allow us to parametrize virtuality/exportability with
the help of an expression (ie selectors, functions, boolean expressions ...)
My $0.02
I think that was worth a lot more that $0.02!
I like that a lot better - virtual and exported are just parameters.
- henrik
--
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: spaceship operator too magical, hard to read
On Fri, May 20, 2011 at 8:20 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7606
>
> The spaceship operator:
>
> User <| group == sysadmin or title == luke |>
>
> 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.:
>
> collect User { group == sysadmin or title == luke }
> User search { group == sysadmin or title == luke }
>
> Please comment on the ticket or reply here, whichever you prefer.
I actually prefer the old syntax because we currently we support the usage of:
User <| title == puppet |> {
noop => true
}
Would the new syntax deprecate this feature? It seems rather confusing to read:
collect User { group == sysadmin or title == luke } { noop => true }
On this subject, should we support regular expression?
User <| title =~ /*adm/ |>
Should we allow referencing of resources using this syntax?
require => User[ group == sysadmin ]
Thanks,
Nan
--
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: exported resource syntax is too magical, hard to read
On Sat, May 21, 2011 at 1:42 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On 20/05/11 22:24, Randall Hansen wrote:
> > http://projects.puppetlabs.com/issues/7612
> >
> > The exported resources syntax:
> >
> > @@user { luke: ensure => present }
> >
> > Is concise and powerful, but very difficult to read. We should
> > consider word-based syntax, e.g.:
> >
> > export @user { luke: ensure => present }
> >
> > And taking into account #7605, perhaps:
> >
> > export virtual user { luke: ensure => present }
> >
> > Please comment on the ticket or reply here, whichever you prefer.
>
> I sincerely hope you'll keep the old syntax around.
>
> I'm terribly sorry to be negative, but I really don't like this kind of
> verbosity.
>
> This is a language, and every language has some idioms. IMHO, newcomers
> should better read the documentation than trying to infer what the
> language does by reading example of it. This feature is an advanced
> feature I don't expect newcomers to grasp in its short or verbose form,
> they'll have to read about it.
>
> One thing I like with the Puppet DSL is that it's concise, you can
> express resources states with the less word possible, yet still be
> readable.
>
> If you really want to simplify people's life, make those extra
> attributes become metaparameters (but please keep the old syntax):
>
> user { luke: ensure => present, virtual => [boolean] }
>
> That would even allow us to parametrize virtuality/exportability with
> the help of an expression (ie selectors, functions, boolean expressions
> ...)
>
>
++
This would be great. Being able to filter on virtual/export status would be
killer.
--
Nigel Kersten
Product, Puppet Labs
@nigelkersten
--
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: spaceship operator too magical, hard to read
+1 from me also, from a newbie's perspective having a verbose syntax
available lowers the barrier to entry.
On May 21, 2011 4:10 AM, "Nathan Clemons" wrote:
> I am very much in favor of this. The current spaceship operator is just
> confusing, hands down. collect and search would be much nicer.
>
> --
> Nathan Clemons
> http://www.livemocha.com
> The worlds largest online language learning community
>
>
>
> On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
>
>> http://projects.puppetlabs.com/issues/7606
>>
>> The spaceship operator:
>>
>> User <| group == sysadmin or title == luke |>
>>
>> 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.:
>>
>> collect User { group == sysadmin or title == luke }
>> User search { group == sysadmin or title == luke }
>>
>> 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.
>>
>>
>
> --
> 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.
Re: [Puppet Users] PC EU feedback: spaceship operator too magical, hard to read
I am very much in favor of this. The current spaceship operator is just
confusing, hands down. collect and search would be much nicer.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7606
>
> The spaceship operator:
>
>User <| group == sysadmin or title == luke |>
>
> 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.:
>
>collect User { group == sysadmin or title == luke }
>User search { group == sysadmin or title == luke }
>
> 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.
>
>
--
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
Verbosity is preferred for readability. +1
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
> 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.
>
>
--
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: long online docs pages should be broken up
I don't think the issue is necessarily that it's all on one page, the hard part for me is that one section bleeds into the next section. It's hard to tell where one leaves off and the next one starts. Some form of break between sections would make it much more readable. -- Nathan Clemons http://www.livemocha.com The worlds largest online language learning community On Fri, May 20, 2011 at 1:18 PM, Randall Hansen wrote: > http://projects.puppetlabs.com/issues/7601 > > Our very long docs pages are difficult to use. E.g., > http://docs.puppetlabs.com/references/2.6.8/type.html > > 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. > > -- 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: exported resource syntax is too magical, hard to read
I would prefer the verbose form as it definitely is much easier to read.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, May 20, 2011 at 1:24 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7612
>
> The exported resources syntax:
>
>@@user { luke: ensure => present }
>
> Is concise and powerful, but very difficult to read. We should
> consider word-based syntax, e.g.:
>
>export @user { luke: ensure => present }
>
> And taking into account #7605, perhaps:
>
>export 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.
>
>
--
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: exported resource syntax is too magical, hard to read
On 20/05/11 22:24, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7612
>
> The exported resources syntax:
>
> @@user { luke: ensure => present }
>
> Is concise and powerful, but very difficult to read. We should
> consider word-based syntax, e.g.:
>
> export @user { luke: ensure => present }
>
> And taking into account #7605, perhaps:
>
> export virtual user { luke: ensure => present }
>
> Please comment on the ticket or reply here, whichever you prefer.
I sincerely hope you'll keep the old syntax around.
I'm terribly sorry to be negative, but I really don't like this kind of
verbosity.
This is a language, and every language has some idioms. IMHO, newcomers
should better read the documentation than trying to infer what the
language does by reading example of it. This feature is an advanced
feature I don't expect newcomers to grasp in its short or verbose form,
they'll have to read about it.
One thing I like with the Puppet DSL is that it's concise, you can
express resources states with the less word possible, yet still be readable.
If you really want to simplify people's life, make those extra
attributes become metaparameters (but please keep the old syntax):
user { luke: ensure => present, virtual => [boolean] }
That would even allow us to parametrize virtuality/exportability with
the help of an expression (ie selectors, functions, boolean expressions ...)
My $0.02
--
Brice Figureau
My Blog: http://www.masterzen.fr/
--
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: long online docs pages should be broken up
On Sat, May 21, 2011 at 12:01 AM, R.I.Pienaar wrote: > > > - Original Message - > > On 2011-05-20 22:18, Randall Hansen wrote: > > > http://projects.puppetlabs.com/issues/7601 > > > > > > Our very long docs pages are difficult to use. E.g., > > > http://docs.puppetlabs.com/references/2.6.8/type.html > > > > I'd disagree on one point. It's not the length of the page that > > bother me, because having all on one page is indeed convenient. But the > > disappearance of the left margin when using a tight browser window > > (firefox 3.6) is annoying. A nice bonus would be to have the content > > list floating alongside the main view, but that's a bit tricky when > > the content is longer that the window height. > > +1 the length is not the problem, in fact I too prefer it all on one page. > > I actually second this. I like having them all on one page. -- 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 wrote:
>
>
> On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
>
>> 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.
Re: [Puppet Users] PC EU feedback: long online docs pages should be broken up
- Original Message - > On 2011-05-20 22:18, Randall Hansen wrote: > > http://projects.puppetlabs.com/issues/7601 > > > > Our very long docs pages are difficult to use. E.g., > > http://docs.puppetlabs.com/references/2.6.8/type.html > > I'd disagree on one point. It's not the length of the page that > bother me, because having all on one page is indeed convenient. But the > disappearance of the left margin when using a tight browser window > (firefox 3.6) is annoying. A nice bonus would be to have the content > list floating alongside the main view, but that's a bit tricky when > the content is longer that the window height. +1 the length is not the problem, in fact I too prefer it all on one page. The problem is in the TOC as indicated above but also since the TOC is simply wrong in some cases. -- 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: long online docs pages should be broken up
On 2011-05-20 22:18, Randall Hansen wrote: http://projects.puppetlabs.com/issues/7601 Our very long docs pages are difficult to use. E.g., http://docs.puppetlabs.com/references/2.6.8/type.html I'd disagree on one point. It's not the length of the page that bother me, because having all on one page is indeed convenient. But the disappearance of the left margin when using a tight browser window (firefox 3.6) is annoying. A nice bonus would be to have the content list floating alongside the main view, but that's a bit tricky when the content is longer that the window height. Regards, N. 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 wrote:
> 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.
Re: [Puppet Users] PC EU feedback: exported resource syntax is too magical, hard to read
On 05/20/2011 01:24 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7612
>
> The exported resources syntax:
>
> @@user { luke: ensure => present }
>
> Is concise and powerful, but very difficult to read. We should
> consider word-based syntax, e.g.:
>
> export @user { luke: ensure => present }
>
> And taking into account #7605, perhaps:
>
> export virtual user { luke: ensure => present }
>
Yes on both counts. My coworkers have often commented on the cryptic
nature of this construct, and googling for 'puppet @@' doesn't return
anything immediately useful. Googling for 'puppet virtual export', on
the other hand, does. In fact, the first hit is the documentation on
Exporting and Collecting Resources.
--
Russell A Jackson
Network Analyst
California State University, Bakersfield
--
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: exported resource syntax is too magical, hard to read
http://projects.puppetlabs.com/issues/7612
The exported resources syntax:
@@user { luke: ensure => present }
Is concise and powerful, but very difficult to read. We should
consider word-based syntax, e.g.:
export @user { luke: ensure => present }
And taking into account #7605, perhaps:
export 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.
[Puppet Users] PC EU feedback: spaceship operator too magical, hard to read
http://projects.puppetlabs.com/issues/7606
The spaceship operator:
User <| group == sysadmin or title == luke |>
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.:
collect User { group == sysadmin or title == luke }
User search { group == sysadmin or title == luke }
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.
[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.
[Puppet Users] PC EU feedback: import should also include subdirectories
http://projects.puppetlabs.com/issues/7604 import "/etc/puppet/manifests/nodes/*" Should import all manifests in subdirectories as well. Note that this conflicts with #4732, which proposes that Puppet globs act more like shell globs. 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.
[Puppet Users] PC EU feedback: long online docs pages should be broken up
http://projects.puppetlabs.com/issues/7601 Our very long docs pages are difficult to use. E.g., http://docs.puppetlabs.com/references/2.6.8/type.html 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.
[Puppet Users] PC EU feedback: ability to remove all unmanaged resources
http://projects.puppetlabs.com/issues/7600
I call this the "agent orange" option :)
This works, purging all unmanaged hosts entries:
resources { 'host':
purge => true,
noop => true,
}
We should have a similar property for all (most?) types.
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.
[Puppet Users] PC EU feedback:
http://projects.puppetlabs.com/issues/7599
This (or something very like it) should work:
file { foo:
ensure => present
mode => 0644
}
Note the lack of commas after key/value pairs.
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.
[Puppet Users] PC EU feedback: unpack array variables in string interpolation
http://projects.puppetlabs.com/issues/7598
If your goal is this (pseudo-code):
@file { "host_one" }
@file { "host_two" }
You should be able to say this:
$array = [ "one", "two" ]
@file { "host_$array" }
Instead of this:
@file { "host_one", "host_two" }
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.
[Puppet Users] PC EU feedback: automatically realize required virtual resources
This an existing ticket, too: http://projects.puppetlabs.com/issues/2084
E.g., given:
@file { foo: ... }
@service { bar:
require => File[ foo ]
}
realize Service[ foo ]
File[ foo ] should also be realized.
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.
[Puppet Users] PC EU feedback: should be able to symlink Puppet's management directories
Several people complained that if Puppet's management directories (e.g., confdir) were symlinks, Puppet would overwrite them with real directories. It turns out that this issue was a ticket already, and an old one. http://projects.puppetlabs.com/issues/650 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.
