Skip to main content

SKU Tooling

Tools and patterns for generating, validating, and auditing EGI SKUs.

Overview​

SKU tooling is implementation-specific. This SOP does not require a single shared repository or legacy tooling package.

Use any internal script, CLI, or CI step that can:

  • generate valid SKU strings
  • validate approved type and platform codes
  • scan codebases or build artifacts for SKU usage when needed

Tool Roles​

Generator​

Generate valid SKUs from version, type, platform, and build date.

Validator​

Validate SKUs against the approved format and code lists.

Auditor​

Scan repos, manifests, or release metadata for missing or invalid SKUs when that level of control is useful.

Reference Usage​

Basic Generation​

sku-tool generate --major 1 --minor 0 --patch 0 --type API --platform EKS

# Output: 1.0.0.API.EKS.20250127

Validation​

sku-tool validate "1.0.0.API.EKS.20250127"

# Output: valid

Scan​

sku-tool scan .

CI/CD Integration​

name: Build

on:
  push:
    tags:
      - "v*"

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Validate release SKU
        run: sku-tool validate "${{ vars.RELEASE_SKU }}"

Governance​

The tooling choice is local to the team. The requirement is that generated SKUs match the documented standard in this section.