This commit is to clean up format of the packages tab. Previously, it just dumped the pkg list to the pane. This change will put it in tabular format with a filter to simplify using the data presented. This commit only includes the name of the package; however, we may want to add additional details in a future commit. Attributes available per package include: name, version, release, arch, epoc, src rpm, filename rpm and sum. This commit also updates the view to use the tupane_layout.
…es pg This commit will order the organizations on Organizations -> List using the same sort order that they are listed on the Roles page. e.g. list as: aaa, AAB, BBB, bbc, ccc, CCD instead of: AAB, BBB, CCD, aaa, bbc, ccc
… all controllers, this stops helper methods with the same name from overwriding each other
widgets to be directly to the right of the filter.
Change introduced in pulp 0.0.237
…configure On Fri, Oct 07, 2011 at 03:50:25PM +0200, Lukas Zapletal wrote: > On 10/07/2011 12:17 PM, Jan Pazdziora wrote: > > > >please review a patch which is a start of moving default values from > >the params.pp files to an answer file, to be able to then merge > >default and custom answer files, plus command line options to > >katello-configure. With the default values in this particular patch, > >it's possible to do > > Pushed, thanks. Going to test it today. > > 84df2c3 Add support for answer files. Hello, attached please find two patches to katello-configure. The first one just rewrites the original shell script to ruby, the second one adds support for command line options and user answer file. The idea here is that if you want some aspect of the project configurable by the user/admin upon the katello-configure time, you will - come up with config value name; - you specify the default value in puppet/default-answer-file (/usr/share/katello/install/default-answer-file); - by doing so, the same value can be used in user's custom file, and will override the default answer file value; - in also enables this name as command-line option to katello-configure (with double dashes and dashes instead of underscores) - the command-line options take precedence over the values previously accumulated from the answer files; - the katello-configure will store the non-default values in /etc/katello/katello-configure.conf; - which is where the puppet manifests will get the information from (besides the default answer file) when you do katello_config_value('config_name') in puppet. Comments in the default answer files are displayed by katello-configure --help and once someone tells me how to best generate man pages from rdoc upon build-time, I plan to put them to the man page as well. This way, there is only one place where options are defined and documented. If this approach sounds sane, I'd ask all engineers to amend the default-answer-file and respective .pp file(s) with values that should be configurable upon katello-configure time. Comments welcome. -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat >From 4ddd914 Mon Sep 17 00:00:00 2001 From: Jan Pazdziora <email@example.com> Date: Tue, 11 Oct 2011 14:39:23 +0200 Subject: [PATCH 1/2] Turn katello-configure to ruby instead of bash.
Don't use merge! for shared test data. Otherwise it causes test fails accidentally.
This commit contains a couple of small fixes to enable saving of favorites for systems and search queries for notices page.