Skip to content

Migration guide from APIOps Toolkit to APIOps CLI #133

Open

Description

@petehauge

Summary

Create documentation (and/or a guided walkthrough) that helps customers migrate from the existing APIOps Toolkit to APIOps CLI.

Problem

Customers currently using APIOps Toolkit need a clear path to adopt APIOps CLI. Without a migration guide, they face uncertainty about:

Proposed Content

1. Conceptual Mapping

  • Side-by-side comparison of Toolkit vs CLI concepts (extractor → apiops extract, publisher → apiops publish, etc.)
  • Differences in artifact format and directory structure

2. Step-by-Step Migration

  • How to initialize a new repo with apiops init
  • How to migrate existing extracted artifacts (or re-extract from scratch)
  • How to convert Toolkit configuration files to CLI configuration format
  • How to update CI/CD pipelines (GitHub Actions / Azure DevOps)

3. Leveraging New Features

4. FAQ / Troubleshooting

  • Common migration pitfalls
  • Breaking changes between Toolkit and CLI

Related

Activity

  1. changed the title [-]docs: Migration guide from APIOps Toolkit to APIOps CLI[/-] [+]Migration guide from APIOps Toolkit to APIOps CLI[/+] on Jun 9, 2026
  2. added
    staleNo activity for 30+ days — will be closed if no further activity
    on Jul 27, 2026
  3. github-actions commented on Jul 27, 2026

    @github-actions

    ⚠️ Stale issue notice — This issue has had no activity for 30 day(s).

    It will be automatically closed after 60 days of inactivity.

    To keep this issue open:

    • Leave a comment describing the current status, or
    • Remove the stale label.

    This notice was posted automatically by the stale issue workflow.

  4. added
    P2Next sprint
    and removed
    staleNo activity for 30+ days — will be closed if no further activity
    on Aug 27, 2026
  5. added
    staleNo activity for 30+ days — will be closed if no further activity
    on Sep 27, 2026
  6. github-actions commented on Sep 27, 2026

    @github-actions

    ⚠️ Stale issue notice — This issue has had no activity for 30 day(s).

    It will be automatically closed after 60 days of inactivity.

    To keep this issue open:

    • Leave a comment describing the current status, or
    • Remove the stale label.

    This notice was posted automatically by the stale issue workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementImprovement to existing functionalityP2Next sprintstaleNo activity for 30+ days — will be closed if no further activity

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions