Progress Software Data Lifecycle API

The DataLifecycle API from Progress Software — 15 operation(s) for datalifecycle.

Operations 15

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

PUT /api/v0/data-lifecycle/compliance/config Configure compliance data retention jobs · SetComplianceConfig configures the compliance data lifecycle scheduler and jobs #
Ask an LLM
“How do I change how long compliance scan data is kept?”
“Can I reschedule the compliance data purge jobs?”
Tell an agent
Set the compliance data lifecycle job settings to {job_settings}.
Update the compliance purge schedule using {job_settings}.
POST /api/v0/data-lifecycle/compliance/run Run compliance data lifecycle jobs now · RunCompliance runs the compliance data lifecycle jobs #
Ask an LLM
“Can I trigger the compliance data cleanup immediately instead of waiting for the schedule?”
“How do I purge old compliance reports right now?”
Tell an agent
Run the compliance data lifecycle jobs now.
Kick off compliance data purging immediately.
GET /api/v0/data-lifecycle/compliance/status Check compliance lifecycle job status · GetComplianceStatus returns the compliance job scheduler status #
Ask an LLM
“When did the compliance data purge last run and when is it next?”
“What is the compliance job scheduler's status?”
Tell an agent
Show the status of the compliance data lifecycle scheduler.
Check whether the compliance purge jobs are running.
PUT /api/v0/data-lifecycle/config Configure all data lifecycle jobs at once · SetConfig provides a singular endpoint for configuring all data lifecycle jobs #
Ask an LLM
“Is there one place to set retention for compliance, event feed, infra and services data together?”
“How do I update every data lifecycle job in a single request?”
Tell an agent
Apply this full data lifecycle configuration: compliance {compliance}, event feed {event_feed}, infra {infra}, services {services}.
Set the infra retention part {infra} in the combined data lifecycle config.
PUT /api/v0/data-lifecycle/event-feed/config Configure event feed data retention jobs · SetEventFeedConfig configures the event feed data lifecycle scheduler and jobs #
Ask an LLM
“How long are event feed entries retained, and can I change it?”
“Can I reschedule the event feed purge job?”
Tell an agent
Set the event feed data lifecycle job settings to {job_settings}.
Change event feed retention with job settings {job_settings}.
POST /api/v0/data-lifecycle/event-feed/run Run event feed data lifecycle jobs now · RunEventFeed runs the event feed data lifecycle jobs #
Ask an LLM
“Can I purge old event feed data immediately?”
“How do I trigger the event feed lifecycle job on demand?”
Tell an agent
Run the event feed data lifecycle jobs now.
Purge expired event feed entries right away.
GET /api/v0/data-lifecycle/event-feed/status Check event feed lifecycle job status · GetEventFeedStatus returns the event feed job scheduler status #
Ask an LLM
“What's the status of the event feed purge scheduler?”
“When will event feed data next be cleaned up?”
Tell an agent
Show the event feed data lifecycle job status.
Check the event feed purge scheduler.
PUT /api/v0/data-lifecycle/infra/config Configure infra node data retention jobs · SetInfraConfig configures the infra data lifecycle scheduler and jobs #
Ask an LLM
“How do I control how long infra data is kept before it is purged?”
“Can I change the schedule of the infra data lifecycle jobs?”
Tell an agent
Set the infra data lifecycle job settings to {job_settings}.
Update infra data retention using {job_settings}.
POST /api/v0/data-lifecycle/infra/run Run infra data lifecycle jobs now · RunInfra runs the infra data lifecycle jobs #
Ask an LLM
“Can I run the infra data cleanup jobs immediately?”
“How do I trigger infra data purging on demand?”
Tell an agent
Run the infra data lifecycle jobs now.
Start infra data cleanup immediately.
GET /api/v0/data-lifecycle/infra/status Check infra lifecycle job status · GetInfraStatus returns the infra job scheduler status #
Ask an LLM
“What is the status of the infra data lifecycle scheduler?”
“When did the infra data cleanup last run?”
Tell an agent
Show the infra data lifecycle job status.
Check the infra cleanup scheduler.
POST /api/v0/data-lifecycle/run Run every data lifecycle job now · Run runs all data lifecycle actions across all data lifecycle jobs #
Ask an LLM
“Can I run all retention and purge jobs across every data type at once?”
“How do I trigger the whole data lifecycle in one go?”
Tell an agent
Run all data lifecycle jobs now.
Trigger every retention and purge action across all data lifecycle jobs.
PUT /api/v0/data-lifecycle/services/config Configure services data retention jobs · Data lifecycle set services config #
Ask an LLM
“How do I set retention for services data?”
“Can I change the schedule of the services data lifecycle jobs?”
Tell an agent
Set the services data lifecycle job settings to {job_settings}.
Update services retention using {job_settings}.
POST /api/v0/data-lifecycle/services/run Run services data lifecycle jobs now · Data lifecycle run services #
Ask an LLM
“Can I run the services data cleanup immediately?”
“How do I trigger the services lifecycle jobs on demand?”
Tell an agent
Run the services data lifecycle jobs now.
Start services data cleanup immediately.
GET /api/v0/data-lifecycle/services/status Check services lifecycle job status · Services #
Ask an LLM
“What is the status of the services data lifecycle jobs?”
“When will services data next be cleaned up?”
Tell an agent
Show the services data lifecycle job status.
Check the services cleanup scheduler.
GET /api/v0/data-lifecycle/status Get aggregate status of all data lifecycle jobs · GetStatus returns the aggregate status across all data lifecycle jobs #
Ask an LLM
“Can I see the status of every data lifecycle job in one response?”
“Are all my retention jobs healthy across compliance, event feed, infra and services?”
Tell an agent
Show the combined status of all data lifecycle jobs.
Give me an overview of every retention scheduler.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/progress-software:progress-software-datalifecycle-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

progress-software-datalifecycle-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  description: '# Authentication

    The Chef Automate API typically uses an API token passed in the header of your API request.'
  title: Chef Automate API Documentation Data Lifecycle API
  termsOfService: https://www.chef.io/terms-and-conditions-of-use/
  contact:
    url: https://www.chef.io/support/
    email: support@chef.io
  license:
    name: Apache 2.0
    url: https://github.com/chef/automate/blob/main/LICENSE
  version: version not set
  x-logo:
    altText: Chef logo
    url: /images/chef-automate-logo.svg
servers:
- url: https://automate.chef.io
tags:
- name: DataLifecycle
  x-displayName: Data Lifecycle
paths:
  /api/v0/data-lifecycle/compliance/config:
    put:
      tags:
      - DataLifecycle
      summary: SetComplianceConfig configures the compliance data lifecycle scheduler and jobs
      operationId: DataLifecycle_SetComplianceConfig
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetComplianceConfigResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetComplianceConfigRequest'
        required: true
  /api/v0/data-lifecycle/compliance/run:
    post:
      tags:
      - DataLifecycle
      summary: RunCompliance runs the compliance data lifecycle jobs
      operationId: DataLifecycle_RunCompliance
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunComplianceResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunComplianceRequest'
        required: true
  /api/v0/data-lifecycle/compliance/status:
    get:
      tags:
      - DataLifecycle
      summary: GetComplianceStatus returns the compliance job scheduler status
      operationId: DataLifecycle_GetComplianceStatus
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetComplianceStatusResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
  /api/v0/data-lifecycle/config:
    put:
      tags:
      - DataLifecycle
      summary: SetConfig provides a singular endpoint for configuring all data lifecycle jobs
      operationId: DataLifecycle_SetConfig
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetConfigResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetConfigRequest'
        required: true
  /api/v0/data-lifecycle/event-feed/config:
    put:
      tags:
      - DataLifecycle
      summary: SetEventFeedConfig configures the event feed data lifecycle scheduler and jobs
      operationId: DataLifecycle_SetEventFeedConfig
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetEventFeedConfigResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetEventFeedConfigRequest'
        required: true
  /api/v0/data-lifecycle/event-feed/run:
    post:
      tags:
      - DataLifecycle
      summary: RunEventFeed runs the event feed data lifecycle jobs
      operationId: DataLifecycle_RunEventFeed
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunEventFeedResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunEventFeedRequest'
        required: true
  /api/v0/data-lifecycle/event-feed/status:
    get:
      tags:
      - DataLifecycle
      summary: GetEventFeedStatus returns the event feed job scheduler status
      operationId: DataLifecycle_GetEventFeedStatus
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetEventFeedStatusResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
  /api/v0/data-lifecycle/infra/config:
    put:
      tags:
      - DataLifecycle
      summary: SetInfraConfig configures the infra data lifecycle scheduler and jobs
      operationId: DataLifecycle_SetInfraConfig
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetInfraConfigResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetInfraConfigRequest'
        required: true
  /api/v0/data-lifecycle/infra/run:
    post:
      tags:
      - DataLifecycle
      summary: RunInfra runs the infra data lifecycle jobs
      operationId: DataLifecycle_RunInfra
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunInfraResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunInfraRequest'
        required: true
  /api/v0/data-lifecycle/infra/status:
    get:
      tags:
      - DataLifecycle
      summary: GetInfraStatus returns the infra job scheduler status
      operationId: DataLifecycle_GetInfraStatus
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetInfraStatusResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
  /api/v0/data-lifecycle/run:
    post:
      tags:
      - DataLifecycle
      summary: Run runs all data lifecycle actions across all data lifecycle jobs
      operationId: DataLifecycle_Run
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunRequest'
        required: true
  /api/v0/data-lifecycle/services/config:
    put:
      tags:
      - DataLifecycle
      operationId: DataLifecycle_SetServicesConfig
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetServicesConfigResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetServicesConfigRequest'
        required: true
      summary: Data lifecycle set services config
      x-summary-source: derived
  /api/v0/data-lifecycle/services/run:
    post:
      tags:
      - DataLifecycle
      operationId: DataLifecycle_RunServices
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunServicesResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/chef.automate.api.data_lifecycle.RunServicesRequest'
        required: true
      summary: Data lifecycle run services
      x-summary-source: derived
  /api/v0/data-lifecycle/services/status:
    get:
      tags:
      - DataLifecycle
      summary: Services
      operationId: DataLifecycle_GetServicesStatus
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetServicesStatusResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
  /api/v0/data-lifecycle/status:
    get:
      tags:
      - DataLifecycle
      summary: GetStatus returns the aggregate status across all data lifecycle jobs
      operationId: DataLifecycle_GetStatus
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetStatusResponse'
        default:
          description: An unexpected error response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/grpc.gateway.runtime.Error'
components:
  schemas:
    chef.automate.api.data_lifecycle.RunComplianceRequest:
      type: object
    chef.automate.api.data_lifecycle.GetComplianceStatusResponse:
      type: object
      properties:
        jobs:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobStatus'
    chef.automate.api.data_lifecycle.GetInfraStatusResponse:
      type: object
      properties:
        jobs:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobStatus'
    chef.automate.api.data_lifecycle.RunRequest:
      type: object
    chef.automate.api.data_lifecycle.SetEventFeedConfigRequest:
      type: object
      properties:
        job_settings:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobSettings'
    chef.automate.api.data_lifecycle.SetInfraConfigResponse:
      type: object
    chef.automate.api.data_lifecycle.SetServicesConfigRequest:
      type: object
      properties:
        job_settings:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobSettings'
    chef.automate.api.data_lifecycle.SetConfigResponse:
      type: object
    chef.automate.api.data_lifecycle.RunServicesRequest:
      type: object
    chef.automate.api.data_lifecycle.RunServicesResponse:
      type: object
    chef.automate.api.data_lifecycle.PurgePolicyUpdate:
      type: object
      title: PurgePolicyUpdate is purge policy configuration update
      properties:
        elasticsearch:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.EsPolicyUpdate'
        postgres:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.PgPolicyUpdate'
    google.protobuf.Any:
      type: object
      properties:
        type_url:
          type: string
        value:
          type: string
          format: byte
    chef.automate.api.data_lifecycle.RunEventFeedResponse:
      type: object
    chef.automate.api.data_lifecycle.SetEventFeedConfigResponse:
      type: object
    chef.automate.api.data_lifecycle.SetServicesConfigResponse:
      type: object
    chef.automate.api.data_lifecycle.RunEventFeedRequest:
      type: object
    chef.automate.api.data_lifecycle.PurgePolicies:
      type: object
      title: PurgePolicies are data lifecycle purge policies
      properties:
        elasticsearch:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.EsPolicy'
        postgres:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.PgPolicy'
    chef.automate.api.data_lifecycle.RunComplianceResponse:
      type: object
    grpc.gateway.runtime.Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        details:
          type: array
          items:
            $ref: '#/components/schemas/google.protobuf.Any'
        error:
          type: string
        message:
          type: string
    chef.automate.api.data_lifecycle.SetComplianceConfigRequest:
      type: object
      properties:
        job_settings:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobSettings'
    chef.automate.api.data_lifecycle.SetComplianceConfigResponse:
      type: object
    chef.automate.api.data_lifecycle.EsPolicy:
      type: object
      properties:
        custom_purge_field:
          type: string
        disabled:
          type: boolean
        index:
          type: string
        name:
          type: string
        older_than_days:
          type: integer
          format: int32
    chef.automate.api.data_lifecycle.EsPolicyUpdate:
      type: object
      properties:
        disabled:
          type: boolean
        older_than_days:
          type: integer
          format: int32
        policy_name:
          type: string
    chef.automate.api.data_lifecycle.RunInfraResponse:
      type: object
    chef.automate.api.data_lifecycle.PgPolicy:
      type: object
      properties:
        disabled:
          type: boolean
        name:
          type: string
    chef.automate.api.data_lifecycle.JobStatus:
      description: 'JobStatus presents the current configuration of job, when it will be executed,

        and details about it''s most recent execution.'
      type: object
      properties:
        disabled:
          type: boolean
        last_elapsed:
          type: string
        last_ended_at:
          type: string
          format: date-time
        last_enqueued_at:
          type: string
          format: date-time
        last_started_at:
          type: string
          format: date-time
        name:
          type: string
        next_due_at:
          type: string
          format: date-time
        purge_policies:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.PurgePolicies'
        recurrence:
          type: string
        threshold:
          type: string
    chef.automate.api.data_lifecycle.PgPolicyUpdate:
      type: object
      properties:
        disabled:
          type: boolean
        policy_name:
          type: string
    chef.automate.api.data_lifecycle.GetServicesStatusResponse:
      type: object
      properties:
        jobs:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobStatus'
    chef.automate.api.data_lifecycle.GetStatusResponse:
      type: object
      properties:
        compliance:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetComplianceStatusResponse'
        event_feed:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetEventFeedStatusResponse'
        infra:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetInfraStatusResponse'
        services:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.GetServicesStatusResponse'
    chef.automate.api.data_lifecycle.RunInfraRequest:
      type: object
    chef.automate.api.data_lifecycle.GetEventFeedStatusResponse:
      type: object
      properties:
        jobs:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobStatus'
    chef.automate.api.data_lifecycle.SetInfraConfigRequest:
      type: object
      properties:
        job_settings:
          type: array
          items:
            $ref: '#/components/schemas/chef.automate.api.data_lifecycle.JobSettings'
    chef.automate.api.data_lifecycle.JobSettings:
      type: object
      title: JobSettings are a job configuration setting update
      properties:
        disabled:
          type: boolean
        name:
          type: string
        purge_policies:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.PurgePolicyUpdate'
        recurrence:
          type: string
        threshold:
          type: string
    chef.automate.api.data_lifecycle.RunResponse:
      type: object
    chef.automate.api.data_lifecycle.SetConfigRequest:
      type: object
      properties:
        compliance:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetComplianceConfigRequest'
        event_feed:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetEventFeedConfigRequest'
        infra:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetInfraConfigRequest'
        services:
          $ref: '#/components/schemas/chef.automate.api.data_lifecycle.SetServicesConfigRequest'
  securitySchemes:
    APIToken:
      description: Authenticate with the Automate API using an API Token.
      type: apiKey
      name: api-token
      in: header
x-tagGroups:
- name: Compliance
  tags:
  - ReportingService
  - StatsService
  - JobsService
  - ProfilesService
  - Comp_Assets
- name: Report Manager
  tags:
  - ReportManagerService
- name: Infra
  tags:
  - ConfigMgmt
  - InfraProxy
- name: Ingest
  tags:
  - ChefIngester
  - JobScheduler
- name: Node Management
  tags:
  - NodeManagerService
  - NodesService
- name: Event Feed
  tags:
  - EventFeedService
- name: Secrets
  tags:
  - SecretsService
- name: Applications
  tags:
  - service_groups
  - retention
  - ApplicationsService
- name: Data Feed
  tags:
  - DatafeedService
- name: Data Lifecycle
  tags:
  - DataLifecycle
- name: Notifications
  tags:
  - Notifications
- name: Content Delivery
  tags:
  - Cds
- name: Audit and Settings
  tags:
  - UserSettingsService
- name: System
  tags:
  - Gateway
  - Deployment
  - License
  - Telemetry
  - LegacyDataCollector
- name: Identity
  tags:
  - users
  - teams
  - tokens
- name: Access Management
  tags:
  - policies
  - roles
  - projects
  - rules
  - Authorization