lr-gladiator 0.33.0

CLI and Python client for Arena PLM (app.bom.com): login, get revisions, list/download attachments, and upload to working revisions.

gladiator-arena

CLI + Python client for interacting with the Arena PLM.

Install

pip install lr-gladiator

Quick start

Login

Interactive login (prompts for username/password):

gladiator login

Non-interactive (for CI/CD):

export GLADIATOR_USERNAME="<insert username>"
export GLADIATOR_PASSWORD="<insert password>"
gladiator login --ci

By default, this stores session details at:

~/.config/gladiator/login.json

Commands

Get the latest approved revision for an item:

gladiator latest-approved 890-1001

Search for items by number pattern:

gladiator list-items 104*

Output JSON instead of a table:

gladiator list-items 104* --format json

List all files on an item (defaults to the latest approved revision):

gladiator list-files 890-1001

Output JSON instead of a table:

gladiator list-files 890-1001 --format json

Display a quick summary for an item revision (number, name, description, category, lifecycle, etc.):

gladiator info 890-1001

Emit machine-readable JSON instead of the Rich table:

gladiator info 890-1001 --format json

The summary includes the Arena web URL (Item URL) so you can click straight into the item from the terminal output.

Download the item's thumbnail (saved as <item>.png/.jpg) while fetching the summary:

gladiator info 890-1001 --picture --rev WORKING

List the Bill of Materials (BOM) for an item:

gladiator get-bom 890-1001

Recursively expand subassemblies up to two levels deep:

gladiator get-bom 890-1001 --recursive --max-depth 2

Add or update a BOM line on the working revision:

gladiator add-to-bom 890-1001 510-0005 --qty 2 --refdes R1

Target a different revision or inspect the raw API response:

gladiator add-to-bom 890-1001 510-0005 --parent-rev EFFECTIVE --format json

Download attached files to a directory named after the article:

gladiator get-files 890-1001

Specify a different output directory:

gladiator get-files 890-1001 --out downloads/

Recursively download all files in the full BOM tree:

gladiator get-files 890-1001 --recursive

Upload or update a file on the working revision:

gladiator upload-file 890-1001 ./datasheet.pdf --category "CAD Data" --title "Datasheet"

Inspect a change and see which views are affected (columns show * when the view is included in the change):

gladiator get-change CCO-0006

Show the raw change payload instead of the Rich table:

gladiator get-change CCO-0006 --format json

Add an item (WORKING revision by default) to an existing change:

gladiator add-to-change --change CCO-0003 510-0001

Create a new change order (effectivity and deadline flags optional):

gladiator create-change --title "Fan bracket update" --description "Replace bracket" --category "Engineering Change Order"

The command prints a summary table with the newly assigned change number. Use --format json to inspect the raw response payload.

3) Output control

Most commands support a JSON output mode.
Example:

gladiator get-bom 890-1001 --output json

Example sessions

Human-readable

$ gladiator list-files 101-1031
         Files for 101-1031 rev (latest approved)         
┏━━━━━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━┳━━━━━━┳━━━━━━━━━━┓
┃ Name            ┃     Size ┃ Edition ┃ Type ┃ Location ┃
┡━━━━━━━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━╇━━━━━━╇━━━━━━━━━━┩
│ 101-1907 E.PDF  │   171396 │ 1       │ FILE │          │
└─────────────────┴──────────┴─────────┴──────┴──────────┘

JSON output

$ gladiator list-files 101-1031 --format json
{
  "article": "101-1031",
  "revision": null,
  "files": [
    {
      "id": "00000000000000000000",
      "fileGuid": "11111111111111111111",
      "name": "101-1907 E.PDF",
      "filename": "101-1907 E.PDF",
      "size": 171396,
      "haveContent": true,
      "downloadUrl": "https://api.arenasolutions.com/v1/files/11111111111111111111/content",
      "edition": "1",
      "updatedAt": "2016-12-06T12:31:33Z",
      "attachmentGroupGuid": "22222222222222222222",
      "storageMethodName": "FILE",
      "location": null
    }
  ]
}

Change inspections use a tabular view that highlights impacted areas. Example output for gladiator get-change CCO-0006:

                Affected items for CCO-0006
┏━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━┳━━━━━━━┳━━━━━━━┳━━━━━━━━┳━━━━━━┓
┃ Item Number ┃ Affected Rev ┃ New Rev ┃ Disposition   ┃ Notes  ┃ BOM ┃ Specs ┃ Files ┃ Source ┃ Cost ┃
┡━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━╇━━━━━━━╇━━━━━━━╇━━━━━━━━╇━━━━━━┩
│ 510-0001    │ A            │ B       │ In Stock: Use │ Review │  *  │       │   *   │        │   *  │
└─────────────┴──────────────┴─────────┴───────────────┴────────┴─────┴───────┴───────┴────────┴──────┘

Programmatic use

Using an existing session

from gladiator import ArenaClient, load_config

client = ArenaClient(load_config())
rev = client.get_latest_approved_revision("890-1001")
files = client.list_files("890-1001", rev)

Programmatic login

Option 1: Direct function call (recommended)

from gladiator import ArenaClient, load_config, arena_login

# Authenticate and save config to current working directory as login.json
arena_login(
    username="[e-mail]",
    password="password",
)

# Now use the client
client = ArenaClient(load_config())

Option 1b: Save to custom path

from pathlib import Path
from gladiator import ArenaClient, load_config, arena_login

# Save config to a specific location
arena_login(
    username="[e-mail]",
    password="password",
    config_path=Path.home() / ".config/gladiator/login.json",
)

# Now use the client
client = ArenaClient(load_config())

Option 2: Login without saving to disk

from gladiator import ArenaClient, arena_login

# Authenticate but don't save
config = arena_login(
    username="[e-mail]",
    password="password",
    save_to_disk=False,
)

# Use the config directly
client = ArenaClient(config)

Option 3: Using environment variables with CLI

import subprocess
import os

# Set credentials
os.environ["GLADIATOR_USERNAME"] = "[e-mail]"
os.environ["GLADIATOR_PASSWORD"] = "password"

# Run login command
subprocess.run(["gladiator", "login", "--ci"], check=True)

# Now use the client
from gladiator import ArenaClient, load_config
client = ArenaClient(load_config())

Development

python -m pip install -e .[dev]
python -m build

FAQ

• Where is the config kept?

  • CLI: ~/.config/gladiator/login.json (override with GLADIATOR_CONFIG)
  • Programmatic arena_login(): Saves to ~/.config/gladiator/login.json by default, or custom path via config_path parameter

• How do I run non-interactively? Make sure to give all required arguments. Also pass --ci to stop output of sensitive information such as username or passwords.

• What does --recursive do? Expands subassemblies and downloads or lists all contained items up to the given --max-depth.

• How does Gladiator handle authentication? It performs a /login call and stores the resulting arenaSessionId for reuse. If it expires, re-run gladiator login.