Skip to main content

NebCLI

NebCLI is the single command-line tool for working with the NebCore platform from your terminal. You sign in once, and from then on NebCLI proves who you are and hands the right short-lived principal and access credentials to the everyday tools you already use: aws, kubectl, helm, and git. It validates Helm charts before they ship and sets up clusters from a written description. One program covers identity, principal and access credentials, validation, and setup, so you do not have to learn or wire together a pile of separate tools.

Why NebCLI​

The problem NebCLI solves is long-lived principal and access secrets. A password-like access credential that lives on many laptops is the thing most likely to leak and stay dangerous after it leaks. NebCLI's delivered access paths never create or store one. When a task needs cloud, cluster, registry, or code-host access, NebCLI asks the platform for a short-lived credential, writes it exactly where the matching standard tool already looks, and steps aside. When that credential expires, NebCLI fetches a fresh one. You get the access you need, scoped to what you are allowed, and no long-lived principal or access secret lingers.

A separate path for platform-owned executor account material is planned, not delivered. Its authorization, custody, and enablement gates remain under review.

What you can do​

  • Sign in through your browser and manage your session, identity, and environments.
  • Get temporary AWS, cluster, GitHub, and chart-registry access for the standard tools.
  • Raise your cloud permissions for a limited time, then give them back.
  • Validate a Helm chart against the platform's rules and every cluster it affects before you merge.
  • Set up and inspect clusters from a written description.
  • Run a self-check that diagnoses sign-in and connectivity problems and tells you how to fix each one.

Learn more​

  • Authentication: sign in, manage contexts and sessions, and run the doctor self-check.
  • Commands: a task-grouped overview of the public commands, exit codes, and output flags.
  • Examples: worked end-to-end tasks, from temporary AWS access to validating a chart.
  • Credential brokering: the current principal and access pattern, plus the separately marked executor-material plan.