Skip to content

Add definitions for missing development tools #145

Description

@andrew

A comparison with dependency parsers and package-manager tooling found several development tools without knowledge definitions in brief.

  • Babashka: bb.edn.
  • OpenTofu: *.tofu.
  • Stack: stack.yaml.
  • Chef: metadata.rb, metadata.json, and Berksfile.
  • BitBake: *.bb and *.bbappend.
  • Buck: BUCK and METADATA.bzl.
  • Devbox: devbox.json and devbox.lock.
  • Jsonnet Bundler: jsonnetfile.json and jsonnetfile.lock.json.
  • Puppet: Puppetfile.
  • Mint: Mintfile.
  • Meteor: package.js, .meteor/versions, and versions.json.
  • Helmfile: helmfile.yaml and its variants.
  • Argo CD: content-matched YAML manifests.
  • Flux: content-matched YAML manifests.

Argo CD and Flux need content-aware matching because they do not have stable filenames. Each new definition should include a focused fixture.

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