Hey Sam, following up from Puppet Conf. Anything I can do to assist with
forthcoming 2.7.x releases? In particular, the full deprecation notices you
mentioned in person would be great to get into a release!
Cheers,
Aaron
On Wednesday, August 21, 2013 3:03:18 PM UTC-7, Sam Kottler wrote:
Please apply the diff from
https://github.com/puppetlabs/puppet-dashboard/pull/226 to resolve the
issue.
On Tue, May 7, 2013 at 6:12 AM, Klavs Klavsen kl...@enableit.dk wrote:
Found out anything about why this is ? Any fix ?
deleting a node hangs puppet-dashboard here :( - I have to restart
Interesting! Let me see if this still happens in the rails3 branch. Please
file a ticket so the issue doesn't get lost.
http://projects.puppetlabs.com/projects/dashboard
On Tue, May 7, 2013 at 11:17 PM, Greg Batye gba...@gmail.com wrote:
Hey everyone,
I have an issue with puppet dashboard
For closure on the thread, this is now fixed in Dashboard 1.2.16.
On Thu, Dec 13, 2012 at 3:19 PM, Luca Gioppo lucagio...@gmail.com wrote:
On a fresh Dashboard installation I get these:
Puppet Dashboard encountered an error.
Something went wrong, and Puppet Dashboard was unable to render
That's a great question! None that I know of, but I could put together some
screenshots.
On Sat, Dec 15, 2012 at 4:12 PM, Jakov Sosic jso...@srce.hr wrote:
On 12/11/2012 12:33 AM, Aaron Stone wrote:
Update: thanks to help from GitHub users @igreg and @astratto, Puppet
Dashboard Rails 3
Please try this PR:
https://github.com/puppetlabs/puppet-dashboard/pull/150
On Fri, Dec 14, 2012 at 11:03 AM, ivan.arsena...@spadz.com wrote:
Change ./app/views/reports/search.html.haml like this :
.item
- if flash[:errors].present?
%div{:class = section error}
%h3
, Aaron Stone sodab...@gmail.com wrote:
Hi all,
Over the past few weeks, I ported the Puppet Dashboard to run on Rails 3
with Ruby 1.8.7. I'm down to only three unit test failures, so I think it's
a good time to share the work and see if anybody else is interested in
continuing Dashboard with me
by viewer/editor/admin access levels.
Cheers,
Aaron
On Fri, Nov 9, 2012 at 4:30 PM, Aaron Stone sodab...@gmail.com wrote:
Hi all,
Over the past few weeks, I ported the Puppet Dashboard to run on Rails 3
with Ruby 1.8.7. I'm down to only three unit test failures, so I think it's
a good time
Hi all,
Over the past few weeks, I ported the Puppet Dashboard to run on Rails 3
with Ruby 1.8.7. I'm down to only three unit test failures, so I think it's
a good time to share the work and see if anybody else is interested in
continuing Dashboard with me.
Rules are not run in order, so there's nothing to indicate to Puppet
which of those contradictory rules should win. Puppet also enforces a
uniqueness on the pair (type, name) -- ('service', 'rsyslog') is
unique and you cannot have another one.
What you'll need to do is make sure that only one of
I'm interested in owning it. I started porting to Rails 3 last week and
have quite a few fixes to the create/update/query endpoints to return more
consistent YAML and JSON responses. At my organization we will continue to
use Puppet Dashboard until Puppet Labs' recommended replacement solution
11 matches
Mail list logo
