agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/infra/openbao/AGENTS.md

nvcf / openbao

AGENTS.md261 starsChanged 9 days agoApache-2.0View on GitHub

This native subtree builds the OpenBao server and JWT plugin image, packages the legacy plugin, and owns the JWT lifecycle driver. See plugins/vault-plugin-secrets-jwt/AGENTS.md for plugin implementation guidance. Run from the repository root: Build from infra/openbao with docker buildx build --platform linux/arm64 --load -t openbao:test .. Run RUNTIME_IMAGE=openbao:test sh scripts/test-runtime-packages.sh there to verify the built image. Check both architectures before release. Keep the legacy image digest and old catalog version aligned with the published pre-bridge image shipped by the chart. Preserve…

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the repository root:

    line 7
  2. Very specific:

    Run RUNTIME_IMAGE=openbao:test sh scripts/test-runtime-packages.sh there to verify the built image.

    line 21
  3. Distinctive:

    Keep the legacy image digest and old catalog version aligned with the published pre-bridge image shipped by the chart.

    line 24
  4. Distinctive:

    Use POSIX shell for packaging and Bash for lifecycle operations.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

OpenBao image

This native subtree builds the OpenBao server and JWT plugin image, packages the legacy plugin, and owns the JWT lifecycle driver. See plugins/vault-plugin-secrets-jwt/AGENTS.md for plugin implementation guidance.

Run from the repository root:

sh infra/openbao/scripts/test-semver.sh
sh infra/openbao/scripts/test-runtime-packages.sh
sh infra/openbao/tests/verify-runtime-ca-test.sh
python3 -B -m unittest discover -s infra/openbao/tests
bash deploy/helm/openbao/tests/jwt-plugin-lifecycle.sh
bash migrations/openbao/tests/jwt-plugin-version-test.sh
shellcheck infra/openbao/scripts/test-runtime-packages.sh

Build from infra/openbao with docker buildx build --platform linux/arm64 --load -t openbao:test .. Run RUNTIME_IMAGE=openbao:test sh scripts/test-runtime-packages.sh there to verify the built image. Check both architectures before release.

Keep the legacy image digest and old catalog version aligned with the published pre-bridge image shipped by the chart. Preserve its plugin bytes; rebuilding the old source changes the stored catalog digest. Compare the legacy plugin executable hash with the published image before claiming catalog compatibility. Keep chart configuration and migration defaults aligned with the image. Bump the target catalog version when changing its source or build inputs.

The live lifecycle BDD uses tests/Dockerfile and tests/bdd/features/openbao-jwt-plugin-lifecycle.feature. See tests/bdd/README.md for isolated runtime qualification. Unit tests use a fake bao and do not qualify server reload, signing, or rollback behavior. Qualify a persistent-state rollout before release. Follow the root QA rules before running live tests.

Use POSIX shell for packaging and Bash for lifecycle operations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free