Polycrate CLI 0.29.0 released: Operator Auto Workspace Resolution and Tools Overhaul

With version 0.29.0, Polycrate receives significant improvements for the Kubernetes Operator and integrated CLI tools.

Operator Auto Workspace Resolution

The Polycrate Operator now automatically detects the associated Workspace and Organization based on the Agent Token. No more manual UUID configuration required!

Before (< 0.29.0):

spec:
  api_sync:
    enabled: true
    credentials_ref:
      secret_name: polycrate-api-creds
      token_key: token
    workspace_id: "550e8400-e29b-41d4-a716-446655440000"  # Manual!
    organization_id: "6ba7b810-9dad-11d1-80b4-00c04fd430c8"  # Manual!

After (0.29.0+):

spec:
  api_sync:
    enabled: true
    credentials_ref:
      secret_name: polycrate-api-creds
      token_key: token
    # workspace_id and organization_id are automatically derived!

Benefits: Easier installation, fewer sources of error, and automatic synchronization with the Polycrate API.

→ Operator Documentation

Tools Overhaul

The polycrate tools command has been stabilized and several critical panics have been resolved:

• Panic with interactive tool selector – Correct argument validation
• Flag conflict in polycrate tools pwgen – Changed -N to -d
• Colors in polycrate tools diff – Enabled by default

All 11 tools now feature comprehensive English --help documentation with structured sections, practical examples, and complete flag descriptions.

→ CLI Reference: Tools

Migration

Operator: Remove workspace_id

If workspace_id and organization_id were configured in OperatorConfig, these fields can now be removed – they are automatically resolved.

Tools: pwgen Flag

The -N shorthand for --numbers has been changed to -d:

# Before (no longer works)
polycrate tools pwgen -N

# After
polycrate tools pwgen -d

→ Full Release Notes

Update Now

polycrate update 0.29.0

Or download the binaries directly from PolyHub.

Polycrate is ayedo’s Infrastructure-as-Code tool for declarative multi-cluster management. Learn more →