agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/control-plane-services/admin-token-issuer-proxy/AGENTS.md

nvcf / admin-token-issuer-proxy

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

Native Go service that mints admin-scoped JWTs through Vault/OpenBao for the self-managed NVCF reference architecture. Run from the monorepo root: CI and release wiring is owned by the monorepo. Do not add a subtree .gitlab-ci.yml, nested Bazel module, Docker release pipeline, or private GitLab import path. - /healthz reports process liveness and must not depend on API Keys. - /readyz remains unavailable until service metadata is cached. - POST /v1/admin/keys must not call Vault before metadata is ready. - Retry…

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the monorepo root:

    line 16

≈ “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 - Admin Token Issuer Proxy

Native Go service that mints admin-scoped JWTs through Vault/OpenBao for the self-managed NVCF reference architecture.

Layout

  • cmd/admin-issuer-proxy/: HTTP server and startup coordination
  • internal/servicecache/: API Keys metadata initialization and retry policy
  • internal/handlers/: liveness, readiness, and token issuance handlers
  • internal/platform/vault/: Vault/OpenBao signing client
  • ../../../deploy/helm/admin-token-issuer-proxy/: deployment chart

Build and test

Run from the monorepo root:

go test ./src/control-plane-services/admin-token-issuer-proxy/... -count=1
go vet ./src/control-plane-services/admin-token-issuer-proxy/...
bazel test //src/control-plane-services/admin-token-issuer-proxy/...
bazel build //src/control-plane-services/admin-token-issuer-proxy/cmd/admin-issuer-proxy:image_index

CI and release wiring is owned by the monorepo. Do not add a subtree .gitlab-ci.yml, nested Bazel module, Docker release pipeline, or private GitLab import path.

Startup contract

  • /healthz reports process liveness and must not depend on API Keys.
  • /readyz remains unavailable until service metadata is cached.
  • POST /v1/admin/keys must not call Vault before metadata is ready.
  • Retry only transient API Keys failures. Permanent configuration, authentication, TLS, response, and metadata errors remain fatal.

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