Skip to content
Argy
Start for free

Consuming Modules

How developers use Argy modules (golden paths) via the portal/CLI to provision, deploy, and operate with guardrails.

In Argy, developers don’t “ask the platform team to do things”. They consume modules (golden paths) through governed self‑service.

Modules are versioned workflows with schemas and governed execution.

What you typically do as a developer

1) Pick a golden path (module)

Start from the module catalog and choose the path that matches your workload.

Use status badges (stable / experimental / deprecated / draft) to select what’s safe to adopt.

2) Configure it (schema-driven)

Deployments are configured from a typed schema (JSON Schema). This is intentional:

  • it makes requirements explicit,
  • it reduces tribal knowledge,
  • it prevents “snowflake” setups.

In practice you fill a configuration form generated from the schema.

3) Apply per environment

Most products have multiple environments (DEV/STG/PRD). With Argy, you can:

  • reuse the same golden path,
  • change only the parameters that differ,
  • apply environment-specific governance (for example: approval required in production).

4) Ship through the portal/CLI

Use the portal when you want visibility and guided flows. Use the CLI when you want automation (CI/CD, scripts) or when the terminal is your default UX.

The key idea: the platform team controls the path, developers control parameters.

5) Follow the run (pipelines)

Each deployment produces runs you can track end-to-end:

  • statuses (QUEUED, WAITING_APPROVAL, RUNNING, SUCCEEDED, FAILED, CANCELED),
  • real-time logs (WebSocket),
  • outputs (structured JSON),
  • artifacts and exports.

You can cancel, retry, approve/reject (when applicable), and export logs and artifacts.

When you need changes

If the golden path is missing something, avoid forking it per team. Prefer:

  1. raising a request to the platform team,
  2. adding an extension point,
  3. releasing a new module version.

That way, improvements are shared and adoption doesn’t fragment.

Next steps