Skip to main content

Dynamic Alias

Dynamic Alias (dya)

A declarative CLI builder that transforms complex command-line workflows into simple, memorable aliases with smart autocompletion.

Why Dynamic Alias?

Modern infrastructure professionals juggle dozens of CLI tools daily—AWS, GCP, Azure, Kubernetes, databases, and more. Each tool has its own syntax, flags, and resource identifiers. Dynamic Alias lets you define once, use everywhere:

# Instead of remembering:
aws ssm start-session --target i-0abc123def456 --region us-east-1

# Just type:
dya ssm prod-web-server

Quick Start

# Install
pip install dynamic-alias

# Create ~/.dya.yaml
echo "
config:
  history-size: 100

---
type: command
name: Hello World
alias: hello
command: echo 'Hello from Dynamic Alias!'
" > ~/.dya.yaml

# Run
dya hello

Documentation

Topic Description
Getting Started Installation, first config, running
Configuration YAML structure, config block, styles
Static Dicts Defining static data sources
Dynamic Dicts Fetching data from external commands, caching, TTL
Commands Aliases, subcommands, arguments
Helper System Auto/custom helper types, array aliases
Features Strict mode, timeout, history
Interactive Mode Shell, autocomplete, history navigation

Examples

Real-world configurations for cloud providers:

Example Description
AWS SSO login, SSM sessions, RDS PostgreSQL, ElastiCache
GCP gcloud auth, Compute SSH, Cloud SQL, Memorystore
Azure az login, VM SSH, PostgreSQL, Redis Cache
OCI oci session, Compute SSH, Autonomous DB, Redis
Custom CLI Building your own branded CLI

Use Cases

Infrastructure Professionals

DBAs, SREs, DBREs, and DevOps engineers who work with multiple tools and dozens of resources daily. Stop memorizing instance IDs—let Dynamic Alias remember them for you.

Companies Building Internal CLIs

Create a declarative, customizable CLI for your organization. Define your company's resources in YAML and distribute a branded tool to your teams.

Roadmap

Recently Added

  • Cache Encryption - Automatic encryption using machine identifier (Windows GUID, Linux/macOS machine-id)

Upcoming

  • OS Package Publishing - Debian (.deb), RPM, Windows installer
  • Homebrew Publication - macOS/Linux via Homebrew

License

MIT License - See LICENSE for details.

Metadata

Release files for dynamic-alias 1.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dynamic-alias 1.1.5
File Size Uploaded
dynamic_alias-1.1.5.tar.gz 85.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dynamic-alias 1.1.5
File Interpreter ABI Platform
dynamic_alias-1.1.5-py3-none-any.whl Python 3 none any Details

Total release size: 133.4 kB

Release files / dynamic_alias-1.1.5.tar.gz

Download URL dynamic_alias-1.1.5.tar.gz
Size 85.5 kB
Tags Source
SHA-256 checksum
How to use checksums
13b01751fc7c2b7ac52f6fc6591086a50c7da8e41514634feb0508d2a081c640
BLAKE2b-256 checksum
How to use checksums
8efd507da2519a707bdb403a501a7eecea1bedd14f859f19c8997be6f409af86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 23, 2026.

Transparency log

Release files / dynamic_alias-1.1.5-py3-none-any.whl

Download URL dynamic_alias-1.1.5-py3-none-any.whl
Size 47.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4eb882d09f889c38952a55804be6092171ace3bbab1165763d3b86a9f3c7df14
BLAKE2b-256 checksum
How to use checksums
55d245f4249b94021d5d97499304cb3185602a28adf3ca045229e45e1db142e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jan 23, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.1.5 This release

2 release files

1.1.4

2 release files

1.1.3

2 release files

1.1.2

1 release file

1.1.1

2 release files

1.1.0

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page