Default DevOps Config exporters

  • Release version: Xanadu
  • Updated March 12, 2026
  • 5 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Default DevOps Config exporters

    The DevOps Config Exporter content pack provides predefined exporters that extract configuration data from deployable snapshots in ServiceNow. These exporters facilitate integration by allowing external tools to consume snapshot data for deployment and provisioning tasks. Note that starting with the Washington D.C. release, DevOps Config is being phased out—it will remain supported but hidden and inactive on new instances.

    Show full answer Show less

    Default exporters cannot be modified directly; however, customers can clone and customize copies. The exporters support multiple output formats such as JSON, YAML, XML, INI, and raw text depending on the exporter.

    Key Exporters and Their Use Cases

    • Return all data (returnAllData-now): Retrieves the entire snapshot content including system folders, useful for full snapshot exports. Does not work if the deployable is deleted.
    • Return all data except vars (returnAllDatanoVars-now): Returns all configuration excluding variables and deployable name—suitable for scenarios where sensitive variable data should be omitted.
    • Return data for a node name (returnDataforNodeName-now): Extracts configuration data for a specified node, optionally including or excluding the node name in the output. Handles errors for non-unique or missing nodes.
    • Return data for a list of nodes (returnDataForNodeNames-now): Retrieves nested configuration data for multiple specified nodes in one request, returning error messages for missing or duplicated nodes.
    • Return data for path (returnDataForPath-now): Returns all configuration data under a specified node path, or entire snapshot if path is empty. Reports errors when path nodes are missing.
    • Return node list for level (returnNodeListForLevel-now): Lists child node names at a specified depth level in the snapshot hierarchy, with option to exclude variable nodes.
    • Return node list for path (returnNodeListForPath-now): Lists immediate child nodes under a specified path, supporting exclusion of variable nodes.
    • Return value for key within a node (returnValueForKeyAtNodeName-now): Retrieves the value of a specified key within a particular node's subtree. Errors occur if multiple matches are found or if key-node combination is missing.
    • Return value for key path (returnValueForKeyPath-now): Returns the value for a key located at a specific node path. Provides error feedback for missing paths or if the requested key is actually a node.
    • Return value for unique key name (returnValueForUniqueKeyName-now): Retrieves the value for a key assumed to be unique across the snapshot. Supports multiple keys but returns an error if duplicates exist. XML and INI formats are not supported.

    Practical Considerations

    • Application and deployable names must be provided as arguments to the exporters.
    • Most exporters support specifying the requested output format to fit integration needs.
    • Error handling varies by exporter, often providing clear messages about missing nodes, keys, or duplicates to assist troubleshooting.
    • Exporters facilitate granular access to snapshot data, enabling precise extraction of configuration elements for automated deployment workflows or data analysis.

    What This Enables for ServiceNow Customers

    These default DevOps Config exporters empower ServiceNow customers to programmatically retrieve detailed configuration data from deployable snapshots. This capability supports automated deployment pipelines, configuration auditing, and integration with external provisioning tools. By leveraging these exporters, customers can efficiently extract exactly the data needed while handling errors gracefully, streamlining DevOps processes within their ServiceNow environments.

    The DevOps Config Exporter content pack contains a set of default DevOps Config exporters of data that can be used as input for further deployment and provisioning activities.

    Important:
    Starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

    DevOps Config exporters allow other tools to consume the data from deployable snapshots.

    Note:
    You cannot modify default exporters. However, you can make a copy of the exporter and customize your copy.
    These exporters are contained in the DevOps Config Exporter content pack.
    • returnAllData-now
    • returnAllData_noVars-now
    • returnDataforNodeName-now
    • returnDataForNodeNames-now
    • returnDataForPath-now
    • returnNodeListForLevel-now
    • returnNodeListForPath-now
    • returnValueForKeyAtNodeName-now
    • returnValueForKeyPath-now
    • returnValueForUniqueKeyName-now

    Return all data (returnAllData-now)

    Returns the full content of the snapshot without any filtering or modifications, including the var system folder.
    Note:
    The exporter fails if the application/deployable is not in Active state (deleted).
    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    Special logic
    None.
    Error handling
    None.

    Return all data except vars (returnAllData_noVars-now)

    Returns all of the configuration data for the deployable, except deployable name and variables.

    Response does not include:
    • vars folder at the deployable level
    • vars folder at each of the included collections
    • Deployable name at the root level of the response
    Note:
    This exporter does not work for deleted applications/deployables.
    Arguments
    Arguments (can be provided on the command line, or entered interactively in run mode).
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    Special logic
    None.
    Error handling
    None.

    Return data for a node name (returnDataforNodeName-now)

    Returns the subset of the snapshot data for a given node name, which is provided as an argument. The argument value must be passed as string text.

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • nodeName - Node name (string, in quotes)
    • includeNodeInOutput - (string, default is true)
    Special logic
    • If nodeName is empty, all data is returned.
    • If includeNodeInOutput is false, the node data is returned excluding the node name.
    Error handling
    • If the nodeName is not unique, multiple instances of nodeName found.
    • If the nodeName is not found, node not found: <nodeName>.
    • If includeNodeInOutput is false and node data is a key-value pair, an error is returned.

    Return data for list of nodes (returnDataForNodeNames-now)

    Returns the full data from the snapshot for a list of nodes. Same as Return data for a node name but returns a nested JSON with configuration data for a list of given node names (including any child nodes).

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • nodeNames - Node names (string, in quotes, comma-separated)
    Special logic
    If nodeNamesList is empty, returns all config data.
    Error handling
    None.
    Response details
    {“node1”:{“contentKey”:”contentValue”},”node2”:{ “error”:”nodeName not found”}}.
    Error handling
    • In case the nodeName is not unique the exporter returns an error response stating “multiple instances of nodeName found” for that specific nodeName. Other nodeNames contain the data
    • If a nodeName is not found it should contain error message for that node

    Return data for path (returnDataForPath-now)

    Returns all of the configuration data for a given node path in the snapshot.

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • nodePath - Node path (string, in quotes)
    Special logic
    If nodePath is empty, return the whole content (similar to all config data).
    Error handling
    If nodePath is not found, the last node name that was not found is stated path not found: <nodeName>.

    Return node list for level (returnNodeListForLevel-now)

    Returns a list of names of nodes that are children of root node at specified level (depth) in the snapshot. For example, level 1 is a direct child of root node, level 2 is a grandchild, etc.

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • ExcludeVarsNode [true|false] - Exclude the vars node from the result (true or false, default is true)
    • nodeLevel - Level of the node (integer, default is 0)
    Special logic
    If no level is specified, then exporter returns the value for level 0 (for example, the deployable root node name).
    Error handling
    None.
    Response details
    [“node1, “node2”, “node3”]

    Return node list for path (returnNodeListForPath-now)

    Returns the list of nodes for a given node path in the snapshot (not taking into account sub-nodes).

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • ExcludeVarsNode [true|false] - Exclude the vars node from the result (true or false, default is true)
    • nodePath - Path to follow with list of nodes separated by pathSeparator (string, in quotes)
    • pathSeparator - Character to separate list of nodePaths (string, default is ‘,’)
    Special logic
    None.
    Error handling
    None.
    Response details
    [“node1, “node2”, “node3”]

    Return value for key within a node (returnValueForKeyAtNodeName-now)

    Returns the value of a specific key that is part of a node in the snapshot. The key can either be directly defined to the node, or lower in the data model to one of the children of the node.

    The difference between this exporter and export value for unique keyName is that the key name only needs to be unique within the subtree of the node.

    Key/node combination is expected to be unique in the snapshot. If the key/node combination is found more than once, there is an error.

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • keyName - Key name (string, in quotes)
    • nodeName - Node name (string, in quotes)
    Special logic
    None.
    Error Handling
    If keyName nodeName combination is not found an empty response is returned.

    Return value for keyPath (returnValueForKeyPath-now)

    Returns the value of a specific key in a specific path.

    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/xml/ini/raw)
    • keyPath - List of node names with key name at the end separated by pathSeparator (string, in quotes)
    • pathSeparator - Character to separate list of keyPaths (string, default is ‘,’)
    Special logic
    None.
    Error handling
    • If the keyPath is not provided, no keyPath argument provided.
    • If the keyPath is not found, states the last node name not found path not found: <path>/<nodeName>.
    • If the keyPath is found and is a node (not a key), keyPath provided is a node and not a key.

    Return value for unique keyName (returnValueForUniqueKeyName-now)

    Returns the value of a specific key based on its name in the snapshot. Unlike export value for key within a node, the key is expected to be unique across the snapshot data model. Multiple keys are supported.
    Note:
    Formats xml and ini are not supported for this exporter.
    Arguments
    • appName - Application name
    • deployableName - Deployable name
    • requestedFormat - Requested format (json/yaml/raw)
    • keyName - Key name (data array)
    Special logic
    If the key is present multiple times in the snapshot, the exporter returns the first value found (returns error).
    Error handling
    • If the keyName is not provided, no keyName argument provided.
    • If the key is not found, key not found: <keyName>.