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

nvcf / openbao

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

This subtree is maintained in this repository. The chart mounts scripts from helm/scripts/ into its initialization Job. Keep shared prerequisite behavior consistent with the standalone deploy.sh. Run focused checks from the repository root: The chart render test requires Helm and yq. Build chart dependencies with make -C deploy/helm/openbao deps. Live deployment needs an explicit test cluster and registry credentials; follow the root QA environment rules. Use Bash and match existing script conventions. Test both standalone script mode and in-cluster helm…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 focused checks from the repository root:

    line 7
  2. Very specific:

    Use Bash and match existing script conventions.

    line 21

≈ “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 deployment and chart

This subtree is maintained in this repository. The chart mounts scripts from helm/scripts/ into its initialization Job. Keep shared prerequisite behavior consistent with the standalone deploy.sh.

Run focused checks from the repository root:

bash deploy/helm/openbao/tests/init-tool-requirements.sh
bash deploy/helm/openbao/tests/auto-unseal-sidecar.sh
bash deploy/helm/openbao/tests/jwt-plugin-lifecycle.sh
python3 -m unittest discover -s infra/openbao/tests
bash migrations/openbao/tests/jwt-plugin-version-test.sh

The chart render test requires Helm and yq. Build chart dependencies with make -C deploy/helm/openbao deps. Live deployment needs an explicit test cluster and registry credentials; follow the root QA environment rules.

Use Bash and match existing script conventions. Test both standalone script mode and in-cluster helm mode when changing initialization prerequisites. The latter must work without a Helm executable in the migration image.

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