Deployment packages
A deployment package captures a specific commit of your policy state, providing a controlled, versioned way to promote finalized policies from development to production.
After policies have been developed, tested, and approved in a branch, they’re bundled into a deployment package for promotion. This ensures deployments reflect a specific reviewed state, reducing the risk of unintended changes.
|
Deployment packages are intended for use in embedded policy decision point (PDP) mode. To export and load policy and Trust Framework data into Policy Editor instances, use snapshots instead. |
Deployment packages offer the following benefits:
-
Predictable policy rollouts: Packages standardize the promotion of policies across environments, reducing the chance of configuration drift or inconsistent deployments.
-
Separation of duties: Policy authors can create and test policies independently, while administrators handle deployment.
-
Auditability and traceability: Each package ties to a specific, versioned policy state, making it easier to track what was deployed and when.
|
The Deployment Packages tab displays up to 100 packages at a time. If a branch contains more than 100 packages, click Load more at the bottom of the list to load the next group of 100 packages. |
Learn more about deployment package operations: