Patch puppet-dashboard for CVE-2012-2660

This commit adds a patch to actionpack to address
CVE-2012-2660, unsafe query generation vulnerability. This
patch is taken from Aaron Patterson on the rails security list:
https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-security/8SA-M3as7A8

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge pull request #102 from MosesMendoza/patch_to_address_CVE_2012_2660

Patch puppet-dashboard for CVE-2012-2660
Install a default settings.yml file with database.yml

Currently dashboard installation lays down a database.yml
file by default. We supply an example settings file with
the package, this commit installs it as well.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge pull request #103 from MosesMendoza/master

Install a default settings.yml file with database.yml
create certs directory with installation

The installation doesn't create a certs directory
under /usr/share/puppet-dashboard, and thus generating
certs can be problematic because of permissions. This
commit adds the certs dir to installation and sets
ownership to puppet-dashboard.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge pull request #104 from MosesMendoza/b70344d1907e1460ea49cf95fdb735bd5d92f378

create certs directory with installation
cleanup on puppet-dashboard spec file

This commit cleans up the puppet dashboard spec file a bit,
adding a dashboard user macro definition, removing some old comments,
and consolidating some sections and commands. It also changes
permissions on settings.yml and database.yml to 0640 instead
of 0644, in line with the packaging for pe-puppet-dashboard.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge pull request #105 from MosesMendoza/maint/master/cleanup_on_spec_file

cleanup on puppet-dashboard spec file
(#11849) Add rake task to install cron job to clean up database reports

This commit adds a rake task to install a monthly cron
job to clean up old database reports, as suggested in official
Puppet Labs documentation. This allows users to easily install
the optional cron job while not risking undesired data loss for
those who do not wish to have the job installed by default.
Merge pull request #106 from Whopper92/cleanup_dashboard_cron

(#11849) Add rake task to install cron job to clean up database reports
Update CHANGELOG for 1.2.10rc1
Update CHANGELOG for 1.2.10
Updated debian postinst script to link properly the settings.yml file to puppet-dashboard config directory.

Otherwise, the application can't find settings.yml and outputs error about invalid setting of daily_run_history_length.
Fixed linking of database.yml in debian postinst to use absolute path.

The file is previously referenced by absolute path, so there is no point in using relative path here. Relative path might change unexpectedly, if the application is moved/installed in a different directory.
Merge pull request #107 from bladealslayer/master

Updated debian packaging postinst script
Add release number variable to packaging rake task

This commit allows the package rake task to be run
with a variable RELEASE value, which allows builds
to be done with a release number of values other than 1.
Merge pull request #108 from Whopper92/package_rake_update

Add release number variable to packaging rake task
(#15523) Update Debian packaging rake task to create the debian and original tarballs

This commit updates the 'package' rake task to create
these tarballs along with the Debian package.
Merge pull request #111 from Whopper92/rake_package_tarballs

(#15523) Update Debian packaging rake task to create the debian and original tarballs
(#15291) Add Vendor tag to Puppet-Dashboard spec file

Previously the spec file had no Vendor tag, which left it undefined. This
commit adds a Vendor tag that references the _host_vendor macro, so that it can
be easily set to 'Puppet Labs' internally and customized by users easily. The
Vendor tag makes it easier for users to tell where the package came from.