indico-cli 0.2.2__tar.gz → 0.4.1__tar.gz

{indico_cli-0.2.2 → indico_cli-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: indico-cli
-Version: 0.2.2
+Version: 0.4.1
 Summary: CLI tool for interacting with Indico event management systems
 Project-URL: Repository, https://gitlab.cern.ch/cern-agent-skills/indico-cli
 License: MIT

{indico_cli-0.2.2 → indico_cli-0.4.1}/indico_cli/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.2.2'
-__version_tuple__ = version_tuple = (0, 2, 2)
+__version__ = version = '0.4.1'
+__version_tuple__ = version_tuple = (0, 4, 1)
 
 __commit_id__ = commit_id = None

{indico_cli-0.2.2 → indico_cli-0.4.1}/indico_cli/cli.py

@@ -71,10 +71,21 @@ def cli(ctx, base_url, token):
 
 @cli.command()
 @click.option("--base-url", required=True, help="Indico instance URL")
-@click.option("--token", default="", help="API bearer token")
+@click.option("--token", envvar="INDICO_API_TOKEN", default="", help="API bearer token (or set INDICO_API_TOKEN)")
 def configure(base_url, token):
     """Configure connection to an Indico instance and test it."""
-    api = IndicoAPI(base_url, bearer_token=token if token else None)
+    if not token:
+        try:
+            token = click.prompt("API token", hide_input=True)
+        except (EOFError, click.Abort):
+            pass
+    if not token:
+        click.echo("Error: no token provided.", err=True)
+        click.echo("Either:", err=True)
+        click.echo("  1. Run in a real terminal: indico-cli configure --base-url URL", err=True)
+        click.echo("  2. Set env var first:  export INDICO_API_TOKEN=indp_... && indico-cli configure --base-url URL", err=True)
+        sys.exit(1)
+    api = IndicoAPI(base_url, bearer_token=token)
     client = IndicoClient(api)
     try:
         result = run_async(client.get_user_info())
@@ -84,6 +95,7 @@ def configure(base_url, token):
         click.echo(f"Configuration saved to {CONFIG_FILE}")
     except Exception as error:
         click.echo(f"Connection test failed: {error}", err=True)
+        click.echo("Check that your token starts with 'indp_' and has the correct scopes.", err=True)
         sys.exit(1)
 
 

{indico_cli-0.2.2 → indico_cli-0.4.1}/skills/indico-skill/SKILL.md

@@ -23,11 +23,13 @@ Set up or update Indico CLI credentials.
 
 1. **Check if already configured**: run `uvx indico-cli user-info 2>&1`. If it returns user info, stop — already configured.
 2. **Ask the user** which Indico instance to connect to (e.g., `https://indico.cern.ch`, `https://indico.fnal.gov`, or a custom URL).
-3. **Guide token creation**: tell the user to open `<base_url>/user/preferences/api`, click "Create new token", name it (e.g., "indico-cli"), select scopes `read:legacy_api`, `write:legacy_api`, `read:user`, click "Create", and copy the `indp_...` token immediately (shown only once).
+3. **Guide token creation**: tell the user to open `<base_url>/user/tokens/`, click "Create new token", name it (e.g., "indico-cli"), select all scopes (you can avoid write in case want to play on the safe side), click "Create", and copy the `indp_...` token immediately (shown only once).
 4. **Save credentials**:
+
    ```bash
    uvx indico-cli configure --base-url <BASE_URL> --token <TOKEN>
    ```
+
    Saves to `~/.config/indico-cli/config.json` (never inside a repo).
 5. **Verify**: the configure command tests the connection automatically. On failure: 403/401 = wrong scopes or expired token; connection error = wrong URL; SSL error = network issue.
 
@@ -44,6 +46,7 @@ If an event returns "not found" or "deleted", don't stop — use `search-by-term
 ### Chaining commands for deeper answers
 
 Many tasks require chaining multiple commands. For example, to find out what someone concluded in a talk:
+
 1. `search-by-term` or `contributions` to find the relevant contribution
 2. `files` or `download` to get the slides/PDF
 3. **Read the downloaded file** and extract the answer
@@ -53,6 +56,7 @@ The goal is to answer the user's question, not just list metadata. If slides wer
 ### Using event IDs from search results
 
 `search-by-term` returns `Event ID` for every contribution, attachment, and note result. Use this ID to drill into the event:
+
 1. `search-by-term --term "my topic"` — find the contribution and note its Event ID
 2. `event-details --event-id <ID>` — get full event info
 3. `contributions --event-id <ID>` — list all contributions
@@ -156,6 +160,7 @@ uvx indico-cli files --event-id <ID> [--download | --no-download] [--download-di
 | `--download-dir` | No | Directory for downloads |
 
 If the built-in download fails (403), list with `--no-download` to get URLs, then use curl:
+
 ```bash
 curl -L -H "Authorization: Bearer $INDICO_API_TOKEN" -o filename.pdf "DOWNLOAD_URL"
 ```
@@ -310,11 +315,13 @@ Used by `create-event-with-agenda`. A JSON array where items with a `contributio
 ## Examples
 
 Search for beam dynamics content:
+
 ```bash
 uvx indico-cli search-by-term --term "beam dynamics" --limit 5
 ```
 
 Create a meeting with agenda:
+
 ```bash
 uvx indico-cli create-event-with-agenda \
   --title "Workshop on ML" \
@@ -328,11 +335,13 @@ uvx indico-cli create-event-with-agenda \
 ```
 
 Download all files from an event:
+
 ```bash
 uvx indico-cli files --event-id 137346
 ```
 
 Schedule a contribution:
+
 ```bash
 uvx indico-cli add-timetable-entry --event-id 137346 --type contribution --object-id 12 --start 2025-06-15T14:00:00 --duration 30
 ```