Deprecate a Published Component

What happens when you deprecate a RightScale component?

When you deprecate a RightScale component, you're only affecting the visibility of that component in the MultiCloud Marketplace.  Deprecated components will no longer be visible in the MultiCloud Marketplace nor will they be importable for new users.  However, a deprecated component will still be usable if required by a Macro.  For example, a user might have previously subscribed to a Macro from the MultiCloud Marketplace that uses a couple different ServerTemplates to create the Servers in a Deployment.  A user will still be able to successfully run the Macro to create the Deployment even if those ServerTemplates have been deprecated.  Remember, a Macro will only import the required ServerTemplates, etc. when it's run.  The same rules apply to ServerTemplates.  If a published ServerTemplate is active in the MultiCloud Marketplace and it references a deprecated MCI, the MCI will be imported when the ServerTemplate is imported.  However, that MCI will not be importable as a standalone component.

Note:  If a component belongs to multiple Account Groups, it cannot be deprecated from one Account Group and active in another.  A component can either be active or deprecated.  Its status applies to all Account Groups in which it's a member.

Deprecate vs. Remove

In order to preserve the functionality of a Macro, you should deprecate its related components instead of removing it from an Account Group or deleting the Account Group(s) that contain those components.   When you delete an Account Group, any components in the Account Group will be removed, not deprecated, which could potentially cause errors.  Deprecated components will not break any dependencies.