insightfactory-cli 1.0.1.dev5__py3-none-any.whl → 1.0.1.dev9__py3-none-any.whl

if_cli/commands/api.py

@@ -61,6 +61,27 @@ def describe_route(document: dict[str, Any], method: str, path: str) -> dict[str
     return operation if isinstance(operation, dict) else None
 
 
+def _is_absolute_http_url(api_path: str) -> bool:
+    parsed = parse_url(api_path)
+    return parsed.scheme in {"http", "https"} and bool(parsed.hostname)
+
+
+def _die_on_misplaced_http_method(api_path: str, positionals: list[str]) -> None:
+    """Explain a `curl`-shaped `if-cli api GET /path`, where the verb is read as the path.
+
+    Recognition spans every verb a user might reach for, not just the ones -X accepts:
+    naming the misplaced verb is more useful than a path error even for TRACE, which
+    -X then rejects on its own terms.
+    """
+    method = api_path.lower()
+    if method not in HTTP_METHODS:
+        return
+    targets = [value for value in positionals[1:] if value.startswith("/") or _is_absolute_http_url(value)]
+    target = targets[0] if targets else "/api/path"
+    suggestion = f"if-cli api -X {method.upper()} {target}"
+    die(f"'{api_path}' looks like an HTTP method, not a path — did you mean: {suggestion} ?")
+
+
 def _die_on_msys_mangled_path(api_path: str) -> None:
     if not WINDOWS_DRIVE_PATH.search(api_path):
         return
@@ -73,11 +94,6 @@ def _die_on_msys_mangled_path(api_path: str) -> None:
     )
 
 
-def _is_absolute_http_url(api_path: str) -> bool:
-    parsed = parse_url(api_path)
-    return parsed.scheme in {"http", "https"} and bool(parsed.hostname)
-
-
 def resolve_api_url(host: str, api_path: str) -> ParseResult:
     if not api_path.startswith("/") and not _is_absolute_http_url(api_path):
         _die_on_msys_mangled_path(api_path)
@@ -145,6 +161,7 @@ def api_command(argv: list[str]) -> None:
     api_path = positionals[0] if positionals else None
     if not api_path:
         die(API_USAGE)
+    _die_on_misplaced_http_method(api_path, positionals)
 
     if values["method"] is not None:
         method = values["method"].upper()

{insightfactory_cli-1.0.1.dev5.dist-info → insightfactory_cli-1.0.1.dev9.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: insightfactory-cli
-Version: 1.0.1.dev5
+Version: 1.0.1.dev9
 Summary: Profile-based authentication CLI for the InsightFactory Interfaces API
 Project-URL: Homepage, https://github.com/insightfactory-ai/insightfactory-cli
 Project-URL: Repository, https://github.com/insightfactory-ai/insightfactory-cli
@@ -102,6 +102,12 @@ prefixes.
 Override the config directory with `INSIGHTFACTORY_CONFIG_DIR` (useful in tests
 and CI). The default is `~/.insightfactory`.
 
+The request method goes in `-X`; `if-cli api` takes exactly one positional
+argument and reads it as the path. A `curl`-shaped `if-cli api GET /api/schedules`
+therefore parses `GET` as the path — write `if-cli api -X GET /api/schedules`
+instead. The CLI names the misplaced verb rather than reporting a problem with
+`/api/schedules`.
+
 On Git Bash (MSYS2) on Windows, path conversion rewrites a leading-slash
 argument such as `/api/agent-projects` into a Windows path. Prefix the command
 with `MSYS_NO_PATHCONV=1`:
@@ -212,12 +218,16 @@ Python 3.10 or newer is required. Runtime code is stdlib-only.
 
 ## Release
 
-Publishing is automatic from GitHub Actions on merge. Verify and build live in
-the reusable workflow
+**A release is cut by pushing a tag, not by merging.** Merging to `main` runs CI and
+publishes nothing.
+
+```bash
+git tag v1.0.1 && git push origin v1.0.1
+```
+
+Verify and build live in the reusable workflow
 [`if_s_insightfactory_cli.yml`](https://github.com/insightfactory-ai/if_sre_github_actions/blob/main/.github/workflows/if_s_insightfactory_cli.yml)
-in `insightfactory-ai/if_sre_github_actions`
-([PR #300](https://github.com/insightfactory-ai/if_sre_github_actions/pull/300)
-must merge before these stubs go green). This repository's
+in `insightfactory-ai/if_sre_github_actions`. This repository's
 `.github/workflows/release.yml` keeps only the OIDC publish job, because PyPI
 Trusted Publishing is registered for **this** repo, workflow `release.yml`, and
 environment `pypi` — a reusable workflow cannot be registered.
@@ -228,24 +238,38 @@ the reusable workflow and uploads it with `pypa/gh-action-pypi-publish`.
 
 | Trigger | Published version | PyPI role |
 |---|---|---|
-| Push / merge to `develop` | `1.0.0.dev{N}` | pre-release (`pip install --pre`) |
-| Push / merge to `main` | `1.0.0` (the version in `pyproject.toml`) | latest |
-| Push of a `v*` tag | same as `main` | retry / explicit cut of that version |
+| Push / merge to `develop` | `1.0.1.dev{N}` | pre-release (`pip install --pre`) |
+| Push of a `v*` tag | the version in `pyproject.toml`, which the tag must match | latest |
+| Merge to `main` | nothing — CI only | — |
 
 `N` is `github.run_number` of the reusable workflow: a per-workflow integer
 that goes up on every run and stays the same across re-runs of that run (so a
 failed publish can be retried under the same version). It does not depend on
-git history or clone depth. After a successful `main` publish, bump `version`
-in `pyproject.toml` on `develop` so later `.devN` builds sort *after* what just
-landed; PEP 440 puts `1.0.0.devN` before `1.0.0`. Because of that ordering, a
+git history or clone depth. After a successful release, bump `version` in
+`pyproject.toml` on `develop` so later `.devN` builds sort *after* what just
+landed; PEP 440 puts `1.0.1.devN` before `1.0.1`. Because of that ordering, a
 dependency spec of `insightfactory-cli>=1.0.0` does not match develop-channel
 `.devN` builds; an in-process consumer that wants them must specify a
 pre-release-bearing spec such as `insightfactory-cli>=1.0.0.dev0` (which also
 matches the final `1.0.0` release).
 
-A version that is already on PyPI is skipped rather than failing, so a second
-push to `main` (or a `v*` tag for the same version) is a no-op. A `v*` tag
-whose name does not match `pyproject.toml` fails before publishing.
+A `v*` tag whose name does not match `pyproject.toml` fails before publishing.
+
+The two channels treat an already-published version differently, on purpose:
+
+- **Release channel (a tag):** publishing fails, naming the fix. A tag is a request to
+  release that version; if it cannot be honoured, the run must say so rather than report
+  success having published nothing. (git also refuses to push a tag that already exists,
+  so this is hard to reach.)
+- **Dev channel (`develop`):** publishing is skipped quietly. `.dev{N}` uses
+  `github.run_number`, which is stable across re-runs of one run, so an already-present
+  version there can only mean a re-run of a run that already published — real idempotency,
+  not a swallowed mistake.
+
+This split is why releasing moved off `main`. While a merge was the trigger, an
+already-published version *had* to be tolerated as a no-op for merges to stay green — so a
+merge that released nothing looked exactly like one that released, and a forgotten version
+bump shipped nothing silently.
 
 ## Differences from the Node CLI
 

{insightfactory_cli-1.0.1.dev5.dist-info → insightfactory_cli-1.0.1.dev9.dist-info}/RECORD

@@ -10,14 +10,14 @@ if_cli/main.py,sha256=0bZZDNoT1NGHeZhH6sD2ZNBTtpYGGTfPTnRIJiGr2vA,2537
 if_cli/oauth.py,sha256=MUvG1aNGpknFfbtblq2Eg86rQv3VM9NrGl4oDgIr5oM,15596
 if_cli/runtime.py,sha256=Pz2iVclqy-uu1UMQWK2P_Hx7O4zAF30UpSFqQvGN0NY,2663
 if_cli/commands/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-if_cli/commands/api.py,sha256=f0hpf6ZzgoX3UNERXVeZi6RsQbAfJnMXQj9EQCVbz70,7499
+if_cli/commands/api.py,sha256=Y759ndF1feZK0IOXjuRWS6v27dvGCTM2mfe72ivwJ_c,8346
 if_cli/commands/config.py,sha256=1KAxjme897NIbXTGBw1rNJlXnFvhbEUf5MAli8A93ns,1724
 if_cli/commands/login.py,sha256=vxsYcRZWsaNEzekyN1zy4ROJO-OCGUpjaVUBhtbK1LY,3255
 if_cli/commands/logout.py,sha256=TW0P4_tXcTtiHHR73xVPHyhlbOWD1jBnkZsMImCiCBw,668
 if_cli/commands/profiles.py,sha256=JNBrYWdHQ9MHauwZxH33IAOYgRYRniX7bwd7KBT6Vyk,3869
 if_cli/commands/set_token.py,sha256=BVyv_QmByvllr04pE2sz8JFEscHbIgOC-7ZPg61PRoc,1886
 if_cli/commands/token.py,sha256=CyiXkyH7vxgH91-n-XJzeHnLI6mZJwO9Js5AHvfHaeM,1120
-insightfactory_cli-1.0.1.dev5.dist-info/METADATA,sha256=5DCZVpYI9OxCWJHNAobvxRCtoDKh14AWrR_8xirXnLk,10880
-insightfactory_cli-1.0.1.dev5.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
-insightfactory_cli-1.0.1.dev5.dist-info/entry_points.txt,sha256=UlX854D7f-7dBj5F0wGdakVy6vopvP9hA1BN-gv739w,44
-insightfactory_cli-1.0.1.dev5.dist-info/RECORD,,
+insightfactory_cli-1.0.1.dev9.dist-info/METADATA,sha256=Vj1zz9rwI1YoZqWM7OMZElRYaTLvIjSCL9gP6iecSls,11987
+insightfactory_cli-1.0.1.dev9.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+insightfactory_cli-1.0.1.dev9.dist-info/entry_points.txt,sha256=UlX854D7f-7dBj5F0wGdakVy6vopvP9hA1BN-gv739w,44
+insightfactory_cli-1.0.1.dev9.dist-info/RECORD,,