Katello/katello — pull request #479 by bbuckingham (2012-08-17 22:09:28+00:00)
Title: DO NOT MERGE: Content deletion - initial merge to master

Reason for 'DO NOT MERGE' - i am seeing 6 tests failing on changeset_spec.rb. It may be only in my env; however, wanted to make the code available for comment while we investigate.

NOTE: Once this is merged to master, developers must run 'rake db:migrate' to pick up the addition of 'type' to the changeset model.

This is the initial merge of the content deletion feature to master. There is still more work to be done; however, we wanted to make the current functionality available to users.

High-level summary:
- UI nav change - usage of 'Promotion' has been replaced with 'Changeset', since you may now create a promotion or deletion changeset.
- UI - ability to associate a type with a changeset (promotion/deletion) during changeset creation
- UI - ability to assign content to a changeset w/ behavior of content tree adjusting to the type of changeset being worked on
- UI - ability to support deletion of products, repos, pkgs, errata, distros and system templates
- UI - various changes to styling to handle the promotion vs deletion concept
- CLI/API - similar capabilities to the above, but from CLI/API point of view

We do have some more testing/hardening to do; however, we'll address that with up upcoming pull requests.