Skip to content

Re-spell examples for musher-dev/spec PR #80 (ADR 0007 renames, ADR 0009 resourceType) #2

Description

@justinmerrell

musher-dev/spec PR #80 renamed document fields across component, blueprint and listing. The platform now requires the new spelling (musher-dev/platform#2670), so any example still using the old names is rejected.

Renames

Was Is
metadata.version metadata.revision
workload.kind workload.type
isRequired, isSensitive, isReadOnly required, sensitive, readOnly
blueprint node component, componentVersion componentRef, revision
advanced placement
sizeGib sizeGiB
cpuArchitecture, acceleratorRuntime cpuArchitectures, acceleratorRuntimes
acceleratorMinVramGb, storageMinIops, acceleratorSkuClass minAcceleratorMemoryGiB, minStorageIOPS, acceleratorSKUClass
semanticType resourceType (a namespaced identifier, for example dev.musher.postgresql.address)

Other rules to follow

  • Omit an optional field rather than writing null. Only schedule: null and a node's size: null survive.
  • Input, output and parameter names, and connection keys, follow ^[a-z][a-zA-Z0-9]{0,63}$. The environment variable a value lands on stays in the input's target.envVarKey.

musher-dev/catalog PR #28 is a worked example of the mechanical re-spell.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions