JFrog Artifactory · Arazzo Workflow

Artifactory Decommission Repository

Version 1.0.0

Read a repository's config, confirm it exists, then delete it.

1 workflow 1 source API 1 provider
View Spec View on GitHub ArtifactsDevOpsCI/CDdocker-registryMavenPackage ManagementRepositoryArazzoWorkflows

Provider

artifactory

Workflows

decommission-repository
Confirm a repository exists, then delete it.
Fetches a repository's configuration to confirm it exists and record its package type, then deletes the repository.
2 steps inputs: accessToken, repoKey outputs: deleteStatus, packageType
1
getRepository
Read the repository configuration to confirm it exists and capture its package type before deletion.
2
deleteRepository
Delete the repository and its content now that its configuration has been confirmed.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Artifactory Decommission Repository
  summary: Read a repository's config, confirm it exists, then delete it.
  description: >-
    A safe teardown flow for JFrog Artifactory. The workflow reads the
    configuration of a repository to confirm it exists and capture its package
    type before deleting the repository and its content. Every step spells out
    its request inline so the flow can be read and executed without opening the
    underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: repositoriesApi
  url: ../openapi/artifactory-repositories-api-openapi.yml
  type: openapi
workflows:
- workflowId: decommission-repository
  summary: Confirm a repository exists, then delete it.
  description: >-
    Fetches a repository's configuration to confirm it exists and record its
    package type, then deletes the repository.
  inputs:
    type: object
    required:
    - accessToken
    - repoKey
    properties:
      accessToken:
        type: string
        description: Bearer access token for authenticating with Artifactory.
      repoKey:
        type: string
        description: The repository key to decommission.
  steps:
  - stepId: getRepository
    description: >-
      Read the repository configuration to confirm it exists and capture its
      package type before deletion.
    operationId: getRepository
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    - name: repoKey
      in: path
      value: $inputs.repoKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      packageType: $response.body#/packageType
      rclass: $response.body#/rclass
  - stepId: deleteRepository
    description: >-
      Delete the repository and its content now that its configuration has been
      confirmed.
    operationId: deleteRepository
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.accessToken
    - name: repoKey
      in: path
      value: $inputs.repoKey
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deleteStatus: $statusCode
  outputs:
    packageType: $steps.getRepository.outputs.packageType
    deleteStatus: $steps.deleteRepository.outputs.deleteStatus

Work with this as data

Every workflow 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 arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • 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 workflow
curl "https://apis.io/api/v1/arazzo/artifactory-decommission-repository-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?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.