plasmactlcomponent

plasmactl-bump

A Launchr plugin for Plasmactl that manages component versioning in Plasma platforms.

Overview

plasmactl-bump automatically updates the version of platform components that were modified in the last commit. It tracks changes using git history and propagates version updates through the dependency tree.

Features

• Automatic Versioning: Updates component versions based on git commit history
• Dependency Propagation: Cascades version updates to dependent components
• Multi-Repository Support: Works across domain and package repositories
• Variable Tracking: Monitors changes in configuration variables (group_vars, vault.yaml)
• Smart Filtering: Excludes documentation files (README.md, README.svg)

Usage

Basic Bump

Update versions of components modified in the last commit:

plasmactl bump

Bump with Sync (Propagation)

Propagate version changes to all dependent components:

plasmactl bump --sync

Important: Always run plasmactl compose before plasmactl bump --sync to ensure accurate dependency resolution.

Options

• --last: Only consider changes from the last commit
• --sync: Propagate versions to dependent resources
• --allow-override: Allow propagation even with uncommitted changes

How It Works

Bump Flow

1. Opens the git repository
2. Checks if the latest commit is not already a bump commit
3. Collects changed files (new, updated, deleted) until the previous bump commit
4. Gets the short hash of the last commit
5. Iterates through resources and updates their versions

Propagation Flow (--sync)

1. Analyze build directory: Identify resources and their dependencies
2. Build timeline: Determine when each resource/variable was last modified
3. Create propagation map: Map version updates chronologically
4. Update resources: Apply propagated versions to dependent components

Component Versioning

Versions are git commit hashes stored in meta/plasma.yaml:

version: abc123def

After propagation, dependent resources get compound versions:

version: original_version-propagated_version

Resource Criteria

Resources must:

• Have a meta/plasma.yaml file
• Match path pattern: %platform/%kind/roles/%name/

Supported component kinds:

• applications
• services
• softwares
• executors
• flows
• skills
• functions
• libraries
• entities

Workflow Example

# 1. Make changes to components
vim platform/services/roles/myservice/tasks/main.yaml

# 2. Commit changes
git add -A
git commit -m "feat: update myservice"

# 3. Bump versions
plasmactl bump

# 4. Compose the platform
plasmactl compose

# 5. Propagate versions to dependencies
plasmactl bump --sync

Multi-Repository Workflow

When working with packages:

# In package repository
vim services/roles/myservice/tasks/main.yaml
git commit -m "feat: update service"
plasmactl bump

# In platform repository
# Update plasma-compose.yaml to reference new package version
plasmactl compose
plasmactl bump --sync

Variable Propagation

Changes to variables in group_vars or vault.yaml trigger propagation to all dependent resources, even without resource bumps:

vim group_vars/platform.interaction.observability/vars.yaml
git commit -m "config: update variable"
plasmactl compose
plasmactl bump --sync  # Propagates variable change to all dependent resources

Documentation

• Plasmactl - Main CLI tool
• Plasma Platform - Platform documentation

License

Apache License 2.0