Packages

Packages are used to move a collection of definitions from one environment to another, typically from a development environment to QA and then to a production environment.

Packages are the core piece of secure promote (see secure promote). A package of definitions can be created by a user in one environment, and then securely imported by an administrator into another environment.

Lifecycle of a Package

Create a package (see Creating a new package)

Users can perform the following:

• Create the initial package of definitions.
• Add or remove definitions in the package.
• Add referenced definitions as needed.
• Replace references as needed.
• Add instructions as needed.
• Validate the package against the local environment.
• Validate the package against a remote environment.

Details of the definitions are not included in the package until it is submitted.

Validating a new package (see Validating a package)

For the included definitions, a local validate will show all definition references that are not included in the package.

A remote validate will show any missing references for the included definitions in respect to the remote scheduler.

Submit an open package (see Packages List)

Details of all definition are added to the package

Package can no longer be modified

Package can be rejected

Package is now available for a remote system to import

Import Package (see Importing a package)

A user with administrator rights can pull a submitted package from another environment

The definitions in the package are not added to the system until the package has been validated and applied

Validating an imported package (see Validating a package)

An administrator can perform the following:

• Review instructions in the package.
• Replace any missing references.
• Replace any references necessary for it to run in the new environment.
• Reject package if needed.

Apply a package (see Packages List)

Definitions in the package are inserted into the current environment.

Folders are created as needed.

Package Statuses

A package will have one of the following statuses:

Status	Description
OPEN	The package can be modified. New definitions can be added. References can be replaced. Instructions can be added.
SUBMITTED	The package has been submitted from on open status. When submitted, the details for each definition in the package are now included in the package. Packages in this mode can now be picked up and imported into a remote environment. The package can no longer be modified.
ACCEPTED	The status of the package on the source scheduler once the package has been accepted into an external scheduler. The status of the external scheduler will be open.
APPLIED	The status of the package in the current scheduler once the package has been applied. When the package is applied, all definitions in the package are inserted/updated in the current scheduler.
PROMOTED	The status shown on the source scheduler once the items from a package have been applied on an target scheduler.
REJECTED	The package has been rejected from a target scheduler. From the source scheduler, the package can be updated and again submitted. From a target scheduler, the package can no longer be modified.