Added initial bindings to changeset. We may decide to go with the inheritance model
soon, depending on the variations in the backend code.

content-deletion - Added action type to  changeset to accomadate content deletion

…angeset

This commit contains the changes to allow user to define the changeset as
either a deletion or promotion changeset.

Updating several of the i18n strings to remove the word 'promotion'
since the changeset will be used to support both promotion and deletion.

As we add in the deletion capability and test, we'll make the distinctions
in the text, where appropriate.

While working on a feature, found that a couple of bugs in being
able to delete packages from a changeset via the changeset sliding
tree.

Once a repo has been promoted to the next environment, it should show
as 'promoted' in the UI and the user should not be adding it
to another changeset to promote again.  (I.e. once the repo is promoted,
the user would promote the pkgs and errata for promotion).  (This is
based upon feedback from the original developer).

Without this commit, the user can promote the same repo over and
over, even if it has already been promoted.   This appears to
be a regression introduced when we added the repository model
to the katello AR.

This commit contains the initial changes needed to allow a user
to add/remove objects to deletion changeset.  Object in this
context include: products, system templates, repositories,
packages, errata and distributions.

In the case of a deletion changeset, the user should be able to add/remove
anything that is in the current environment.

In the case of a promotion changeset, the user should only
be able to add content based upon the previous established rules
(e.g. product promoted to next env, object not already promoted...etc)

When user views the details for a changeset on the promotions
page, they should see that it is either for deletion or promotion.

At this time, user cannot edit the changeset type, since doing
so could completely invalidate some of the content in the changeset.

When viewing a changeset from the changeset history, include the
type as part of the information displayed.

content-deletion - a few UI commits

content-deletion - fix broken spec

When a changeset is created, it is associated with an environment.
This commit will associate the changeset with the proper environment
based upon the type of changeset.

In the case of a deletion changeset, it needs to be associated with
the current environment (e.g. dev, if in dev env).

In the case of a promotion changeset, it needs to be associated with
the next environment where the content is being promoted to
(e.g. if in dev and next env is test, it would be set to test).

In the previous commit, we updated the logic to associate
proper environment with the changeset based upon the
changeset action (promotion/deletion); however, the
specs needed some updates to account for this change.

When the user is in the Library, only allow for changesets of
type 'promotion'.  Do not allow for 'deletion' changesets.

With content-deletion, we are adding the ability to support both
promotions and deletions of content.  The current navigation is
worded such that it indicates support of only promotions.

Based on feedback/discussion on mailing list, updating the navigation
from:

  Content -> Changeset Promotions -> Promotions
                                  -> Changeset Promotion History

to:

  Content -> Changset Management -> Changesets
                                 -> Changesets History

…n cs type

This small commit updates the 'play' button text to set it to delete or
promote based upon the type of changeset that is currently open.

Content deletion

content deletion - few more UI commits

Moving to an inheritance model where changeset class is now
split as PromotionChangeset and DeletionChangeset.
A 'type' column was added to changests table instead of the action_type
so that the rails model works naturally

Changeset refactor

…dling

This commit fixes a bug that I introduced :( when adding support
for content deletion.

…atus)

This is the initial integration commit between the javascript and controller
to support deletion changesets.  The old 'promote' action is now
'apply' supporting both promotion and deletion.  The old 'promotion_progress'
action is now 'status', to be consistent with other controllers.

This is a small commit that will bypass checking for dependencies
when a deletion changeset is to be applied.  For now, we will
allow the request to be made, but skip the check.  In the future,
the plan is to perform such checks.

When the user goes to the Changesets page for a given environment,
we need to list any working deletion changes for that environment
and any promotion changesets for the next environment.

Previously, we'd always show 'all' working changesets that
are in the next environment; however, that does not work properly
for deletion changesets.

content-deletion - a few random commits for UI

…age delete workign at this point

content deletion - adding back in the CLI promote and apply

Package delete changes

…elete

Package  Delete via changeset

This commit contains changes needed to process deletion
of errata that are in a deletion changeset.

This commit contains changes needed to process deletion
of distros that are in a deletion changeset.

content-deletion - add backend support for ...

This commit contains changes needed to process deletion
of repos that are in a deletion changeset.

When we refactored the changeset in to multiple classes, changeset
creation no longer defaulted to 'promotion'.  This commit addresses
that.

…ric)

Currently, when a changeset is processed, there is status text indicating
(promoting, promotion failed, promoted...); however, this text does
not make sense for a deletion changeset.  Changing the text to be
'applying', 'apply failed' and 'applied' in order to be generic.

We may want to reword this later, however, we may not need to once the UI
better reflects the changeset type.

…ame change

…s pg)

This commit contains a couple of minor changes for the changeset history page:
1. support listing the 'deleted' changesets
2. support searching based on "type:promotion" and "type:deletion". Without
   this particular change, the user would have to search using
   PromotionChangeset and DeletionChangeset

content-deletion - add backend support for ...

also a to_json method on changeset to propery output type

content deletion - proper deletion support in the CLI

Master content delete merge

This commit contains some minor changes to be able to handle
deletion changesets within the last environment of the environment
path.  Since previously only promotions were supported, the
'New Changeset' link, changeset sliding tree and changeset actions
were not applicable; however, now we need them.

This commit contains some minor changes to also begin to introduce
a permission check for deletion changesets.  The behavior of
this will be altered as we update the permission model and introduce
the UI changes based on UXD input; however, this gets the current
functionality working in that last environment.

… env

This commit changes the behavior of repo deletion (via content deletion)
to support the following:

1. If the repo being deleted is in the last environment of the environment
   path (e.g. in Test when path is Libary->Dev->Test), delete it

2. If the repo being deleted is in the middle of the environment path
   (e.g. in Dev when path is Library->Dev->Test), disable and unpublish
   the repo.  This leaves the repo, but makes it appear to be gone
   from the user perspective.  Also, if the repo is repromoted,
   it will be enabled and published, making it available again.

Updating the converge-ui version

…-deletion

This reverts commit 94f166a.

Content deletion

content-deletion - fixes for handling deletion of repos... and deletion of content from last env

… pulp

(cherry picked from commit a68b8ca4d78f17ef3cf24429cb1108071717245b)

This is an initial commit to add a banner to the changeset sliding
tree to allow a user to view either promotion or deletion changesets...

This was suggested in the pull request

Speeded up package deletion and promotion

…ntent-deletion-3

unit test fixes

…n/promotion)

This is an initial commit to provide changes to support the appearance
of 2 separate sliding trees for promotion and deletion changesets.

There is more work to be done to get this to work when applying the
changesets...etc.

…eadcrumb

If the user accesses the changesets page with a changeset hash
(e.g. "#changeset=changeset_10") and that changeset is a
deletion changeset, load the page with the deletion changeset
sliding tree selected; otherwise, use the default behavior which
is to load the page with the promotion changeset sliding tree
selected.

…sting

Previously we had a single list consisting of all changesets.  In
that listing, we included some text to indicate the type for each
changeset (i.e. deletion/promotion).  Since we are now creating 2
separate lists, that type is no longer necessary; therefore, removing it.

Quick fix to a bug introduced in the package deletion and promotion

…Remove'

This commit contains changes so that when an item (e.g. product, pkg,
errata...) is added to the changeset, the content tree includes
"Added (Undo)" (where undo is a link) vs "Remove".  Although this
affects the content tree (left side), it does not affect the changeset
tree (right side), which will continue to use 'Remove'.

This commit also contains a small fix to allow repos to be removed
from a changeset after they have been added.  Previously there was
a bug where the repo once added was not correctly detected by
the changeset 'has_item' method.

…Remove'

This is a follow-up to the previous commit to address the changes needed
to the system templates view.

This commit adds the title attribute to the items in the
changeset action bar (e.g. Remove, Edit Details, Review, Promote/Edit).
For simplicity/efficiency, chose to use html title attribute for
these vs creating a tipsy element.

Update to have a custom confirm on changeset deletion, so user
is aware of the type of changeset they are deleting.

Added a tipsy to the 'Added' text in the content tree so that
when user hovers, they see info like "Added to changeset XYZ".

Added title attribute to changeset actions (e.g. Remove, Edit..etc);
however, noticed that tipsy is used in this page quite a bit but
title is not.  As a result, updated them to use tipsy for consistency.
Also, added a 'tipsify' class so that we can have a single instantiation
of tipsy for the tipsies added for the actions, the ones used for
the "Added (Undo)" and others in the future.

…ntent-deletion-3

content-deletion - changes to UI based on mockups

This commit addresses the issue where the notices generated
for a successful promotion or deletion changeset was a
'sticky message'.

This commit contains a small fix to address an issue where if
the user goes to the 'last' environment, they do not see the
any deletion changesets listed on page load.

content-deletion - 2 small fixes

Added system template deletion feature