You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/plan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -439,7 +439,7 @@ This section identifies content in `specs/` that should be adapted for user-faci
439
439
|`specs/spec.md`| Product specification — internal design document, not user-facing. |
440
440
|`specs/tasks.md`| Task tracking — project management artifact, not user documentation. |
441
441
|`specs/research.md`| Internal research on API client patterns and alternatives considered. Useful for contributors but not end users. |
442
-
|`specs/v1-research-report.md`| Internal analysis of v1 APIOps toolkit. Useful reference material for writing `guides/migration-from-v1.md` but not directly publishable. Keep as source material. |
442
+
|`specs/v1-research-report.md`| Internal analysis of APIOps Toolkit. Useful reference material for writing `guides/migration-from-v1.md` but not directly publishable. Keep as source material. |
443
443
|`specs/checklists/`| Requirements checklists — project artifacts, not user-facing. |
444
444
|`specs/contracts/`| Interface contracts (cli-commands.md, iapim-client.md, iartifact-store.md) — internal API design, not user documentation. |
Comprehensive mapping of all APIM REST API resource types against v1 APIOps coverage, v2 APIOps planned coverage, and rationale for inclusion/exclusion.
5
+
Comprehensive mapping of all APIM REST API resource types against APIOps Toolkit coverage, APIOps CLI planned coverage, and rationale for inclusion/exclusion.
6
+
7
+
## Definitions
8
+
9
+
-**APIOps Toolkit** — the original, community-maintained APIOps solution built on Azure Pipelines / GitHub Actions workflows. Source: <https://github.com/Azure/apiops>
10
+
-**APIOps CLI** — the newer, standalone command-line tool that replaces the Toolkit with a more general-purpose, technology-agnostic approach. Source: <https://github.com/Azure/apiops-cli>
6
11
7
12
## Legend
8
13
@@ -14,9 +19,9 @@ Comprehensive mapping of all APIM REST API resource types against v1 APIOps cove
14
19
15
20
## Service-Level Resources
16
21
17
-
| # | Resource Type | ARM Path |v1 APIOps | v2 APIOps | Should Cover | Notes |
| 22 | Product Api Link |`/products/{name}/apiLinks/{link}`| ❌ | ❌ | ❓ | Newer association model. May replace Product Api (#17) in future. Monitor. |
46
51
| 23 | Product Group Link |`/products/{name}/groupLinks/{link}`| ❌ | ❌ | ❓ | Newer association model. May replace Product Group (#18) in future. Monitor. |
47
52
48
53
## API Resources
49
54
50
-
| # | Resource Type | ARM Path |v1 APIOps | v2 APIOps | Should Cover | Notes |
Copy file name to clipboardExpand all lines: specs/spec.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -196,7 +196,7 @@ The development team wants the CLI to support adding new top-level commands (e.g
196
196
-**SC-003**: The `--dry-run` mode accurately predicts 100% of changes that a subsequent publish would make.
197
197
-**SC-004**: Incremental publish (commit-based) processes only changed resources, completing in under 30 seconds for typical single-API changes.
198
198
-**SC-005**: The tool runs successfully in GitHub Actions and Azure DevOps pipelines using service principal authentication without any manual intervention.
199
-
-**SC-006**: Existing APIOps v1 users can point the new tool at their existing artifact directories and successfully publish without restructuring their files.
199
+
-**SC-006**: Existing APIOps Toolkit users can point the new tool at their existing artifact directories and successfully publish without restructuring their files.
200
200
-**SC-007**: Adding a new top-level command requires creating only the command module — no changes to existing command files, the main entry point, or shared infrastructure.
201
201
-**SC-008**: Unknown APIM properties introduced in newer API versions are preserved through extract-edit-publish cycles with zero data loss.
202
202
-**SC-009**: A new user can go from an empty repository to a working CI/CD pipeline (with extract and publish stages) by running `apiops init` and following the outputted identity-setup instructions, completing the process in under 15 minutes.
@@ -206,7 +206,7 @@ The development team wants the CLI to support adding new top-level commands (e.g
206
206
207
207
- Users have an Azure subscription with permissions to read and write APIM resources (Contributor or equivalent role on the APIM instance).
208
208
- The Azure APIM REST API remains stable within a given API version; the tool targets a default version but allows override.
209
-
- The v1 APIOps artifact directory layout is the established convention and maintaining compatibility is strongly preferred over a new layout.
209
+
- The APIOps Toolkit artifact directory layout is the established convention and maintaining compatibility is strongly preferred over a new layout.
210
210
- Internet connectivity is available when running extract and publish (offline-only workflows are out of scope).
211
211
- The tool is distributed as an npm package and/or standalone binary; distribution mechanism details are deferred to implementation planning.
212
212
- APIM API secrets (named value values marked as secrets, subscription keys) are NOT extracted in plaintext — they must be handled via override configuration or key vault references.
Copy file name to clipboardExpand all lines: specs/v1-research-report.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# APIOps v1 Research Report: Scenarios, Requirements & Edge Cases
1
+
# APIOps Toolkit Research Report: Scenarios, Requirements & Edge Cases
2
2
3
-
> **Purpose**: Extract every user scenario, requirement, and edge case the v2 rebuild must support
3
+
> **Purpose**: Extract every user scenario, requirement, and edge case the APIOps CLI rebuild must support
4
4
5
5
---
6
6
@@ -542,7 +542,7 @@ Authentication is handled by `Azure.Core.Pipeline.BearerTokenAuthenticationPolic
542
542
543
543
### 5.6 Circular Dependencies
544
544
545
-
Not explicitly handled. The PUT/DELETE ordering is **hardcoded** in `App.cs`, not dynamically computed. The ordering was manually determined to avoid dependency conflicts. The v2 architecture proposes topological sort via `DependencyGraph`.
545
+
Not explicitly handled. The PUT/DELETE ordering is **hardcoded** in `App.cs`, not dynamically computed. The ordering was manually determined to avoid dependency conflicts. The APIOps CLI architecture proposes topological sort via `DependencyGraph`.
546
546
547
547
### 5.7 Long-Running Operations
548
548
@@ -625,7 +625,7 @@ All mirror service-level equivalents under `/workspaces/{name}/`:
0 commit comments