Re: [Puppet Users] UX/UI of puppet help when face actions have unmet dependencies
On Thu, Jun 28, 2012 at 8:00 PM, Daniel Pittman dan...@puppetlabs.com wrote: No, mentioning STDERR is terrible UX, even if I know what it means. :) I think a better approach would be to capture the error and report it meaningfully. The mockup does that, albeit before the rest of help output. I think we were too wedded to keeping errors on STDERR. Including them again in STDOUT below the help sounds better. You should separate unavailable subcommands from available subcommands entirely - display them in a distinct section of the help output. I disagree. They should stay in the list and in alphabetical order so that customers don't have to look to hard for them. That doesn't obviate your (excellent) suggestion to include them below as well. You should consider colour in this, as recent changes to UX include colour highlights through the text - see the module tool for examples. +1 r -- 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] UX/UI of puppet help when face actions have unmet dependencies
On Fri, Jun 29, 2012 at 10:22 AM, Daniel Pittman dan...@puppetlabs.com wrote: So, perhaps the title of that should change from available subcommands to all subcommands or something? That was the key part that, to me, was worth making that change - that these were absolutely *not* available, because they were broken. Probably we should instead say Subcommands or Puppet subcommands. r -- 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] puppet module... remove?
On Fri, May 11, 2012 at 9:43 AM, Pieter van de Bruggen pie...@puppetlabs.com wrote: The connection to the Forge is being established to try to resolve dependencies; the `--ignore-dependencies` flag (which is implied by `--force`) is what you're looking for. :) Do we need a more explicit offline mode of operation? I'm not sure the docs are good enough for people to see this. r -- 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] difficulty installing dashboard.
On Tue, Jan 24, 2012 at 8:46 AM, Michael Stahnke stah...@puppetlabs.com wrote: Which docs? I swear we've had this updated. These, Mike: http://docs.puppetlabs.com/guides/installing_dashboard.html. I've pinged Nick Fagerlund about a fix. Apologies for the bother, Peter. We have this documented in too many places. r -- 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] difficulty installing dashboard.
On Tue, Jan 24, 2012 at 10:56 AM, Peter Berghold salty.cowd...@gmail.com wrote: rake aborted! no such file to load -- rdoc/task You may have other issues (aside from the mass of deprecation warnings ... ew), but this makes it look like you're missing the rdoc gem. r -- 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] can we alter the 30-min run time?
On Thu, Nov 3, 2011 at 8:38 AM, Nigel Kersten ni...@puppetlabs.com wrote: In your puppet.conf agent block: ... # The maximum time to delay before runs. Defaults to being the same as the # run interval. # The default value is '$runinterval'. splaylimit = 1800 Having this uncommented as this value is a noop, right? ... # Whether to sleep for a pseudo-random (but consistent) amount of time before # a run. splay = false I think we should document this better; I don't feel any closer to being able to solve this problem. I would probably set splay to true and hope that it worked, but it wouldn't surprise me if I had to go back and tweak something else. I also can't tell if you're just telling Jo to read the fine manual, or if you're suggesting configuration values which will solve the problem. (Don't anyone take this as a flame on Nigel; he's sitting 6 feet away from me right now :) r -- 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] Need feedback on Dashboard/filebucket interaction
Good people ~ We're in an unfortunate situation with Dashboard, having to patch a bug half-way for the Dashboard 1.2 release because we don't have time for a complete fix, and because a complete fix may require Puppet changes. Within Dashboard's report interface we show links to the filebucket even if we don't have the file in question. If there's no content, we show an unhelpful error. The silly part is that we can't easily tell if we have file content without asking filebucket directly, which won't scale. We can address it in two ways: 1. Always show the links, just like we do now. If there's no content, show a helpful error when the link is clicked. 2. Only show the links where we know we have content. But in some situations (e.g., a new file) content will be available, but we won't show a link. This is because filebucket only works as a backup, not as a cache for new content. If this affects your life, or if you have an opinion, please comment on the bug or reply here. Thanks in advance. http://projects.puppetlabs.com/issues/7934 r -- 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] Re: Why?
On Thu, Aug 11, 2011 at 12:40 AM, ki_chi_saga fan...@kth.se wrote: See the little arrows? No i didn't I think that this is more common than we suspect. It's been on my list for a while, now I have a ticket: http://projects.puppetlabs.com/issues/8923 Maybe what we're doing now cannot be improved, but I'll keep thinking about it. Feedback welcome. r -- 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] two possibilities for declaring resources with hashes [was: Virtual resources and hashes]
I think Aaron lays out the options pretty well. This issue has been hanging fire for quite a while, and it would be nice to come to a decision about what our path forward is. Who else cares about this? What do you think? r On Wed, Jun 8, 2011 at 1:36 PM, Aaron Grewell aaron.grew...@gmail.com wrote: We've looked at two different possibilities thus far: 1) Make all resource types hash-aware. This is what I was originally asking for. It would mean changing the way resources are declared so that in the case of a hash their representation of $name was appropriate for use with defines and virtuals. This could either be done by requiring the hash to have a 'name' key and using that or by creating a metaparameter like hash_key so it could be user-specified. The hash itself would need to be passed to the resource in the same way as $name but with a different identifier so that its keys could be accessed inside the resource as e.g. $data[key]. The upside of this is that it should work universally and conceptually match the rest of Puppet, the downsides I see so far are that its implementation might well be intrusive and it might also add to the DSL. 2) Create a hash - resource transformation function. If I understood John correctly this is what he was in favor of. The upside of this is it should be less intrusive, easier to implement, and require no DSL changes. The downside is that it still makes hashes special and requires separate handling of them. -- 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] Virtual resources and hashes
On Tue, Jun 7, 2011 at 4:15 PM, Aaron Grewell aaron.grew...@gmail.com wrote:
$users = [{ username = bill, uid = 12345 },
{ username = ted, uid = 12346 }]
Aaron, I think this is a completely sane request. We've talked about
it before, but I can't find an existing ticket. This one seems close,
but very old; will you take a look?
http://projects.puppetlabs.com/issues/1858
If we can work out a good syntax we'll put this on the roadmap. I
know some of our PS guys are eager for it, too.
r
--
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] Re: Virtual resources and hashes
On Wed, Jun 8, 2011 at 12:07 PM, Aaron Grewell aaron.grew...@gmail.com wrote: All I'm saying is that I think hashes should be first-class citizens in Puppet and right now they're not. I agree with that as a high-level problem statement, but to make progress we need to put legs on it. John's got one possibility: a new built-in function. I agree with him that the DSL is too crufty, but I don't think this needs to add to it if done well. Here's another possibility, I think: http://groups.google.com/group/puppet-users/browse_thread/thread/162d86ed39d6d8da What do you think? I must admit not to understand all the details. As D. UX I mostly try to squeeze ideas out of other people. :) I'll try to keep the conversation going and help us coalesce around the details, but I'll need help from people who really have skin in the game. Thanks, r -- 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] puppet dashboard 404s
On Sat, May 28, 2011 at 5:36 AM, Tim Dunphy bluethu...@gmail.com wrote: I noticed that it complained that it couldn't find this file /usr/share/puppet-dashboard/public/stylesheets/all.css This is actually one of the more straightforward aspects of Ruby on Rails. Everything in the public directory is served directly by the webserver. This error likely means that the server running Dashboard can't find that directory. I looked on the system and couldn't find it (tho I am not sure that is causing the problem) this is one of the errors I see (I am looking for others).. a lot of info was output to the screen when I tried to load that page here is more output that I saw to the screen. This looks like log output from importing reports. I haven't read every line, but nothing jumps out as wrong. what logs should I be looking at for clues? It depends on how you're running Dashboard. Apache? Passenger? Using `script/server` locally? How did you install Dashboard? From source, or a package? With a little more information this should be an easy problem. r -- 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] Dashboard and GDGraph and or data visualization module
On Wed, Apr 27, 2011 at 10:34 AM, Aaron Lippold lipp...@gmail.com wrote: I was wondering if anyone has started on looking at a general data graphing framework for visualizing data ( classes, facts, reports ) on dashboard. In the past I have used GDGraph to do this. Has the community talked about how we want to generalize this for the dashboard? Aaron, I haven't. The new summary reporting going into Dashboard 1.2 is very simple, and a graph library is overkill. In the future we hope to do more, though. What particular things are you looking to graph? r -- 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: 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: 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: 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: 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: 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: 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] resources type: only for purge?
Good people ~ Is the resources type primarily useful for purging? Is it also commonly used for metaparameters? The documentation[1] says this, but I haven't used it much myself, and I don't know what common use is. Thanks! r 1. http://docs.puppetlabs.com/references/stable/type.html#resources (Search for metatype to see it; the resources anchor is bugged.) -- 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] What do you use import for?
Good people ~ I'm running through the Puppet DSL trying to understand it. Some parts seem a little funky, like import. Before I start forming any silly opinions, tell me: what do you use import for? Does it serve that purpose well, or do you grimace a little every time you type it? Thanks! r -- Randall Hansen • Director of User Experience • rand...@puppetlabs.com -- 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] dashboard and classes
On Tue, Apr 12, 2011 at 4:20 PM, Mohamed Lrhazi lrh...@gmail.com wrote: Can I import all my existing classes/modules into the dashboard, or do I have to create them in the GUI? Today you have to use the GUI. We know this is a problem, and have concrete plans to fix it: http://projects.puppetlabs.com/issues/3503 r -- 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] puppet-dashboard
On Apr 4, 2011, at 4:03 AM, FRLinux wrote: On Mon, Apr 4, 2011 at 11:53 AM, Patrick kc7...@gmail.com wrote: Then the db:raw:optimize command will actually be able to shrink the DB. Note, that attribute will cause all tables to be stored in separate files. Nice one, thanks for all the replies, I have a responsive dashboard once again :) Steph Patrick ~ We're aware of some performance problems in Dashboard and are keen to fix them. How much data do you have? How many nodes? How many unresponsive? What's your update interval? At what point does it start to fall over? Thank you! r -- Randall Hansen • Director of User Experience • rand...@puppetlabs.com -- 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] pupet dashboard taking more than 10 minutes to destroy a node
On Mar 24, 2011, at 9:06 AM, Stefan Goethals wrote: Dashboard removes the reports for nodes one by one... This can take a long time with many reports. If this is true (and I have no reason to doubt it), it's Very Bad. I've filed it as a bug: http://projects.puppetlabs.com/issues/6828 If this affects you, please watch the bug. r -- 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] Re: Puppet Dashboard - Blank Run Time Chart in Node Details
On Mar 8, 2011, at 7:44 AM, Robert Pumphrey wrote: I also have a completely blank Run Time chart on a new deployment of dashboard 1.0.4. Do you have any idea where I might look to try to fix this problem? I see this, too. I'll track it down and post an update here. r -- Randall Hansen • Director of User Experience • rand...@puppetlabs.com -- 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] Use cases for role-based access?
Good people ~ I'd like to collect real-life use cases for role-based access in Dashboard. I have a few on our wiki, e.g.: * Only production operators can assign groups or nodes to production machines http://projects.puppetlabs.com/projects/dashboard/wiki/RoleBasedAccess Please chime in with what you need, either via email or by editing the wiki. I'm more than happy to insert your cases into the wiki if you don't want to sign up for an account. Thank you! r -- Randall Hansen • Director of User Experience • rand...@puppetlabs.com -- 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] Proposal: strict mode for manifests
On Mar 8, 2011, at 2:37 PM, Robin Bowes wrote: I'd really like puppet to blow-up at this stage and tell me that I've used an variable without defining it first. Those familiar with perl will recognise this as use strict;. ++ r -- Randall Hansen • Director of User Experience • rand...@puppetlabs.com -- 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] Role-based access in Dashboard
On Mar 7, 2011, at 3:39 PM, John Warburton wrote: Everything everyone else has said plus audit logging of actions taken by the user, and ways to report on that (even a last x changes on the node view) Yes, absolutely. RBAC is incomplete without good auditing. r -- 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] Role-based access in Dashboard
Denmat wrote: Very high level but I would like to see the following: • to be able to create roles such as viewer, editor, administrator • these roles be ldap groups Den, will you tell me more about roles being LDAP groups? To my perception that could mean: * Manually creating a role in Dashboard and associating it with an LDAP group, * Importing groups from LDAP to then manipulate as roles in Dashboard, * LDAP groups being read-only in Dashboard and represented as roles, * something else I've not considered. Thank you, r -- 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: Dashboard write API (was Re: [Puppet Users] Role-based access in Dashboard)
On Mar 3, 2011, at 1:40 PM, Brian Gupta wrote: Absolutely. I'll keep your name on my list, and we'll make our plans in public. Any sense on a timeframe? Not at all. I don't like that answer either, but it's the only truth we have. We'll have a better idea when our roadmap for Dashboard improves. r -- 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] Role-based access in Dashboard
Good people ~ Role-based access will be one of the next big features in Dashboard. If this is something that would help you, will you tell me the minimum features that you would consider useful? That is, the features without which RBAC would be useless to you. I'm sure there'll be disagreement; right now I'm just gathering requirements. Once we have feedback from multiple channels we'll work on prioritizing and creating a roadmap. Thanks! r -- Randall Hansen; Director of User Experience; rand...@puppetlabs.com -- 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.
