agentleFS
NVIDIAKnown publisherNVIDIA/nvcf/src/control-plane-services/encrypted-secret-store/AGENTS.md

nvcf / encrypted-secret-store

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

ESS is an OSS/self-hosted Java service in the root nvcf Bazel module. It is Bazel-only in this monorepo. Do not add project POMs, Maven settings, nested Bazel configuration, or a component dependency lock. Run commands from the monorepo root with a full JDK 25: Integration tests are tagged requires-docker. They use Testcontainers and need a running Docker daemon. Do not remove or modify pre-existing local containers, clusters, or volumes during validation. The executable is: See BAZEL.md for focused tests, generated…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 commands from the monorepo root with a full JDK 25:

    line 9
  2. Distinctive:

    Do not generate or publish Maven-shaped ESS artifacts from Bazel.

    line 42
  3. Very specific:

    Do not copy the standalone repository's root LICENSE, NOTICE, internal CI configuration, or Maven repository settings into this subtree.

    line 55

≈ “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

AGENTS.md - Encrypted Secret Store

ESS is an OSS/self-hosted Java service in the root nvcf Bazel module. It is Bazel-only in this monorepo. Do not add project POMs, Maven settings, nested Bazel configuration, or a component dependency lock.

Build and test

Run commands from the monorepo root with a full JDK 25:

export BAZEL_OUTPUT_USER_ROOT="${TMPDIR:-/tmp}/nvcf-bazel-cache"

bazel --output_user_root="${BAZEL_OUTPUT_USER_ROOT}" \
  build //src/control-plane-services/encrypted-secret-store/...

bazel --output_user_root="${BAZEL_OUTPUT_USER_ROOT}" \
  test //src/control-plane-services/encrypted-secret-store/... \
  --cache_test_results=no \
  --test_output=errors

Integration tests are tagged requires-docker. They use Testcontainers and need a running Docker daemon. Do not remove or modify pre-existing local containers, clusters, or volumes during validation.

The executable is:

bazel-bin/src/control-plane-services/encrypted-secret-store/ess-service/app.jar

See BAZEL.md for focused tests, generated outputs, NOTICE, Docker, and local startup commands.

Dependencies

The root MODULE.bazel and maven_install.json own @nv_third_party_deps. BUILD targets must declare direct compile and runtime edges. Use direct source labels for co-located nv-boot libraries.

Do not generate or publish Maven-shaped ESS artifacts from Bazel.

NOTICE

The component NOTICE is derived from the exact jars in the Bazel app:

bazel run //src/control-plane-services/encrypted-secret-store:generate_notice -- \
  --update-metadata --write
bazel test //src/control-plane-services/encrypted-secret-store:notice_check_test
bazel build //src/control-plane-services/encrypted-secret-store:osrb_dependency_delta

Do not copy the standalone repository's root LICENSE, NOTICE, internal CI configuration, or Maven repository settings into this subtree.

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.

Reviews can't be read right now.

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.