PingAuthorize

Publishing to a deployment package store

To use the Deployment Manager feature, create a deployment package and publish it to a deployment package store.

Before you begin

You must configure the Policy Editor to publish policies to your deployment package store using an options file.

For more information, see Configuring the Policy Editor to publish to a deployment package store.

About this task

To publish deployment packages to a deployment package store:

Steps

  1. Export a snapshot.

    For more information, see Exporting a policy snapshot.

  2. Go to Branch Manager > Deployment Packages.

  3. Click the icon.

  4. Enter a meaningful name for your deployment package.

  5. In the Branch list, select a policy branch.

  6. In the Commit list, select a commit.

  7. In the Policy Node list, select a policy node.

    Example:

    Screen shot of the Deployment Packages tab of the Branch Manager settings, with a new policy deployment package created as specified

  8. Click Create Package.

  9. Click the Deployment Manager tab.

  10. In the Deployments pane, select the deployment package store you want to publish the policies to.

  11. In the Available Packages list, select the deployment package you want to publish to the deployment package store.

  12. Click Deploy.

Result

Your deployment package is visible in your configured deployment package store.

Example

If you configured an Amazon Simple Storage Service (S3) bucket for your deployment package store, your published deployment package objects should be visible on the Objects tab of your bucket in Amazon Web Services (AWS) Management Console.

Depending on your configured prefix, AWS may have produced an object hierarchy. If so, drill into the hierarchy to locate your published deployment package.
Screen capture showing two published deployment packages on the Objects tab of an S3 bucket within the S3 dashboard of AWS Management Console

Next steps

Add the deployment package store to the PingAuthorize Server for read access. Based on your deployment package store configuration, add one of the following: