Contents x
    PDQ Connect - Deploy Package
    • 22 Sep 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    PDQ Connect - Deploy Package

    • Updated on 22 Sep 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    PDQ Connect - Deploy Package deploys missing software/packages to devices in PDQ Connect for:

    • Devices that match the results of the selected saved query, and match the Enforcement Action Dynamic Value statement, if defined, or devices selected on the Devices page.

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    Note:

    General Settings

    • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
    • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

    Note:

    This enforcement action runs on Device assets.

    • Use stored credentials from PDQ Connect Adapter - Select this option to use the PDQ Connect connected adapter credentials.

      • When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
      • When not enabled, see Connection Parameters

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Package ID/Package Version ID - The IDs of the software packages to deploy to the devices. Add a package ID, and then click Enter for each additional package ID.

    • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.


    Additional Fields

    These fields are optional.

    Connection and Credentials

    When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

    • Host Name or IP Address - The hostname or IP address of the [PDQ Connect] server.
    • API Key - An API Key associated with a user account that has permissions to perform this action. For information on how to obtain an API Key, see the PDQ Connect API.
    • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
    • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
    • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.
    • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the  HTTPS Proxy.
    • Gateway Name - Select the Gateway through which to connect to perform the action.

    APIs

    Axonius uses the PDQ Connect API.
    Endpoint: Swagger UI

    • POST /v1/api/deployments - Deploys a package version to the target devices or groups.


    For more details about other Enforcement Actions available, see Action Library.


    Was this article helpful?
    What's Next