Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
address greptile comments
adilson7a29db9a98b8
diff --git a/.gitignore b/.gitignoreindex b90ecb360e..d76691b5c7 100644--- a/.gitignore+++ b/.gitignore@@ -58,6 +58,7 @@ yarn-error.log*.env.infisical# Infisical init+.infisical.yaml.infisical.json.infisicalignorediff --git a/docs/cli/faq.mdx b/docs/cli/faq.mdxindex e20d6cbdf8..776943eba2 100644--- a/docs/cli/faq.mdx+++ b/docs/cli/faq.mdx@@ -64,7 +64,7 @@ Yes. If you have previously retrieved secrets for a specific project and environ</Accordion>-<Accordion title="Can I upload the `.infisical.json` file that was generated?">+<Accordion title="Can I upload the `.infisical.yaml` file that was generated?">Yes. This is simply a configuration file and contains no sensitive data.</Accordion>diff --git a/docs/cli/overview.mdx b/docs/cli/overview.mdxindex d550c2f995..1620cbf11a 100644--- a/docs/cli/overview.mdx+++ b/docs/cli/overview.mdx@@ -26,7 +26,7 @@ Install the CLI, log in, and connect it to a project:Upgrade the CLI to the latest version</Card><Card title="Project configuration" icon="file-cog" href="/cli/project-config">- Link a directory to an Infisical project with `.infisical.json`+ Link a directory to an Infisical project with `.infisical.yaml`</Card></CardGroup>diff --git a/docs/cli/reference.mdx b/docs/cli/reference.mdxindex 56913b6b6c..b623c679db 100644--- a/docs/cli/reference.mdx+++ b/docs/cli/reference.mdx@@ -193,11 +193,11 @@ The configuration can't include secret templates. To render secrets as well, usecommand="dynamic-secrets"usage="[flags]"flags={[- { name: "--env", value: "<string>", type: "string", default: "dev", description: "The environment to work in. Every `infisical dynamic-secrets` subcommand accepts it. Defaults to the [environment set in `.infisical.json`](/cli/project-config#set-the-environment), then `dev`." },+ { name: "--env", value: "<string>", type: "string", default: "dev", description: "The environment to work in. Every `infisical dynamic-secrets` subcommand accepts it. Defaults to the [environment set in `.infisical.yaml`](/cli/project-config#set-the-environment), then `dev`." },{ name: "--output", short: "-o", value: "<string>", type: "string", description: "Print the dynamic secrets as `json`, `yaml`, or `dotenv` instead of a table." },{ name: "--path", value: "<string>", type: "string", default: "/", description: "The folder to list dynamic secrets from." },{ name: "--project-slug", value: "<string>", type: "string", description: "The slug of the project to list dynamic secrets from. Takes precedence over `--projectId`." },- { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project to list dynamic secrets from. Without it or `--project-slug`, the CLI uses the project in `.infisical.json`. Can also be set with `INFISICAL_PROJECT_ID`." },+ { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project to list dynamic secrets from. Without it or `--project-slug`, the CLI uses the project in `.infisical.yaml`. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--token", value: "<string>", type: "string", description: "A machine identity access token to authenticate with, instead of your login. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`." },]}examples={[@@ -237,7 +237,7 @@ Create, list, renew, and delete the leases of a dynamic secret.{ name: "--plain", type: "bool", description: "Print each credential as `KEY=value`, one per line, with no other output. Ignored when you pass `--output`." },{ name: "--principals", value: "<string>", type: "string", description: "The principals to put in the certificate, separated by commas. Required by SSH dynamic secrets, and each one must be allowed by the dynamic secret." },{ name: "--project-slug", value: "<string>", type: "string", description: "The slug of the project that holds the dynamic secret. Takes precedence over `--projectId`." },- { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the dynamic secret. Without it or `--project-slug`, the CLI uses the project in `.infisical.json`. Can also be set with `INFISICAL_PROJECT_ID`." },+ { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the dynamic secret. Without it or `--project-slug`, the CLI uses the project in `.infisical.yaml`. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--token", value: "<string>", type: "string", description: "A machine identity access token to authenticate with, instead of your login. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`." },{ name: "--ttl", value: "<string>", type: "string", description: "How long the lease lasts, such as `30m` or `1h`. Defaults to the dynamic secret's default TTL, and can't exceed its max TTL." },]}@@ -268,7 +268,7 @@ The table and `--plain` show only credentials whose values are strings. Pass `--{ name: "--output", short: "-o", value: "<string>", type: "string", description: "Print the deleted lease as `json`, `yaml`, or `dotenv` instead of a table." },{ name: "--path", short: "-p", value: "<string>", type: "string", default: "/", description: "The folder that holds the lease's dynamic secret." },{ name: "--project-slug", value: "<string>", type: "string", description: "The slug of the project that holds the lease. Takes precedence over `--projectId`." },- { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the lease. Without it or `--project-slug`, the CLI uses the project in `.infisical.json`. Can also be set with `INFISICAL_PROJECT_ID`." },+ { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the lease. Without it or `--project-slug`, the CLI uses the project in `.infisical.yaml`. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--token", value: "<string>", type: "string", description: "A machine identity access token to authenticate with, instead of your login. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`." },]}inheritedFlags={[@@ -294,7 +294,7 @@ Delete a lease before it expires, and revoke its credentials with the provider.{ name: "--output", short: "-o", value: "<string>", type: "string", description: "Print the leases as `json`, `yaml`, or `dotenv` instead of a table." },{ name: "--path", short: "-p", value: "<string>", type: "string", default: "/", description: "The folder that holds the dynamic secret." },{ name: "--project-slug", value: "<string>", type: "string", description: "The slug of the project that holds the dynamic secret. Takes precedence over `--projectId`." },- { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the dynamic secret. Without it or `--project-slug`, the CLI uses the project in `.infisical.json`. Can also be set with `INFISICAL_PROJECT_ID`." },+ { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the dynamic secret. Without it or `--project-slug`, the CLI uses the project in `.infisical.yaml`. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--token", value: "<string>", type: "string", description: "A machine identity access token to authenticate with, instead of your login. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`." },]}inheritedFlags={[@@ -320,7 +320,7 @@ List the active leases of a dynamic secret, with each lease's ID, expiry time, a{ name: "--output", short: "-o", value: "<string>", type: "string", description: "Print the renewed lease as `json`, `yaml`, or `dotenv` instead of a table." },{ name: "--path", short: "-p", value: "<string>", type: "string", default: "/", description: "The folder that holds the lease's dynamic secret." },{ name: "--project-slug", value: "<string>", type: "string", description: "The slug of the project that holds the lease. Takes precedence over `--projectId`." },- { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the lease. Without it or `--project-slug`, the CLI uses the project in `.infisical.json`. Can also be set with `INFISICAL_PROJECT_ID`." },+ { name: "--projectId", value: "<string>", type: "string", description: "The ID of the project that holds the lease. Without it or `--project-slug`, the CLI uses the project in `.infisical.yaml`. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--token", value: "<string>", type: "string", description: "A machine identity access token to authenticate with, instead of your login. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`." },{ name: "--ttl", value: "<string>", type: "string", description: "How long to extend the lease by, from its current expiry, such as `30m` or `1h`. Defaults to the dynamic secret's default TTL." },]}@@ -341,7 +341,7 @@ Extend a lease before it expires, and print its new expiry time. A renewal can'tcommand="export"usage="[flags]"flags={[- { name: "--env", short: "-e", value: "<string>", type: "string", default: "dev", description: "The environment to export secrets from, such as `dev`, `staging`, or `prod`. Defaults to the [environment set in `.infisical.json`](/cli/project-config#set-the-environment), then `dev`." },+ { name: "--env", short: "-e", value: "<string>", type: "string", default: "dev", description: "The environment to export secrets from, such as `dev`, `staging`, or `prod`. Defaults to the [environment set in `.infisical.yaml`](/cli/project-config#set-the-environment), then `dev`." },{ name: "--expand", type: "bool", default: "true", description: "Resolve secret references and shell parameter expansions in secret values. Pass `--expand=false` to export values exactly as stored. It takes effect only when you authenticate with a token; with your login, the CLI always resolves them." },{ name: "--format", short: "-f", value: "<string>", type: "string", default: "dotenv", description: "The output format: `dotenv`, `dotenv-export`, `dotenv-eval`, `csv`, `json`, or `yaml`." },{ name: "--include-imports", type: "bool", default: "true", description: "Include secrets imported into the environment from other environments or folders." },@@ -485,7 +485,7 @@ Stop and remove a gateway's systemd service. Run the command as root on Linux.command="init"usage="[flags]"flags={[- { name: "--project-id", value: "<string>", type: "string", description: "Project ID to link this directory to. When set, skips the interactive org and project pickers and writes `.infisical.json` directly." },+ { name: "--project-id", value: "<string>", type: "string", description: "Project ID to link this directory to. When set, skips the interactive org and project pickers and writes `.infisical.yaml` directly." },]}examples={[{ title: "Link the current directory to a project", code: "infisical init" },@@ -494,12 +494,12 @@ Stop and remove a gateway's systemd service. Run the command as root on Linux.]}>-Link the current directory to an Infisical project. The command lists the projects in your profile's organization and writes the one you choose to `.infisical.json`, so later commands in this directory and its subdirectories know which project to use. It needs a user login, and starts one if you have no profile.+Link the current directory to an Infisical project. The command lists the projects in your profile's organization and writes the one you choose to `.infisical.yaml`, so later commands in this directory and its subdirectories know which project to use. It needs a user login, and starts one if you have no profile.-If `.infisical.json` already exists in the current directory, the command asks before replacing it. The new file holds only the project ID, so settings you added, such as `defaultEnvironment`, are lost. See [project config](/cli/project-config) for the file format.+If the current directory already has an `.infisical.yaml` or a legacy `.infisical.json`, the command asks before writing a new `.infisical.yaml`. The new file holds only the project ID, so settings you added, such as `default-environment`, no longer apply. To keep the settings in a legacy `.infisical.json`, [convert it](/cli/project-config-migration) instead of running `init`. See [project config](/cli/project-config) for the file format.<Note>- If you run `init` without a terminal, such as in CI or from a script, the command never prompts. It exits with an error unless you pass `--project-id`, and it doesn't replace an existing `.infisical.json`. To link a different project, edit `workspaceId` in `.infisical.json`.+ If you run `init` without a terminal, such as in CI or from a script, the command never prompts. It exits with an error unless you pass `--project-id`, and it doesn't replace an existing `.infisical.yaml` or legacy `.infisical.json`. To link a different project, edit `secrets-management.project-id` in `.infisical.yaml`.</Note></CLICommand>@@ -1178,7 +1178,7 @@ Stop and remove a relay's systemd service. Run the command as root on Linux.Delete all the data the CLI stores on your machine and return it to its default state. Use it when a problem persists and you want a clean start.-The command revokes the session of every profile on the server, then deletes every profile's credentials from your system keyring and deletes the `~/.infisical` directory. That directory also holds cached secrets and the credentials that gateways, relays, and KMIP servers saved when you ran them as a non-root user, so those are deleted too. A session that can't be revoked stays valid until it expires, and the command prints a warning for it. `.infisical.json` files in your projects aren't touched.+The command revokes the session of every profile on the server, then deletes every profile's credentials from your system keyring and deletes the `~/.infisical` directory. That directory also holds cached secrets and the credentials that gateways, relays, and KMIP servers saved when you ran them as a non-root user, so those are deleted too. A session that can't be revoked stays valid until it expires, and the command prints a warning for it. `.infisical.yaml` and `.infisical.json` files in your projects aren't touched.Log in again with [infisical login](/cli/reference#login) afterwards. Directory bindings are deleted with the rest of the configuration, and terminals pinned with [infisical profile pin](/cli/reference#profile-pin) point to a profile that no longer exists.@@ -1193,11 +1193,11 @@ Log in again with [infisical login](/cli/reference#login) afterwards. Directory]}flags={[{ name: "--command", short: "-c", value: "<string>", type: "string", description: "A shell command to run instead of the arguments after `--`, such as `\"npm run build && npm start\"`. Use it to chain several commands." },- { name: "--env", short: "-e", value: "<string>", type: "string", default: "dev", description: "The environment to fetch secrets from, such as `dev`, `staging`, or `prod`. Defaults to the [environment set in `.infisical.json`](/cli/project-config#set-the-environment), then `dev`." },+ { name: "--env", short: "-e", value: "<string>", type: "string", default: "dev", description: "The environment to fetch secrets from, such as `dev`, `staging`, or `prod`. Defaults to the [environment set in `.infisical.yaml`](/cli/project-config#set-the-environment), then `dev`." },{ name: "--expand", type: "bool", default: "true", description: "Resolve secret references and shell parameter expansions in secret values before injecting them. Pass `--expand=false` to inject values exactly as stored." },{ name: "--include-imports", type: "bool", default: "true", description: "Include secrets imported into the environment from other environments or folders." },{ name: "--path", value: "<stringArray>", type: "stringArray", default: "/", description: "The folder to fetch secrets from. Repeat the flag to inject secrets from several folders. When a secret exists in more than one, the value from the last `--path` wins." },- { name: "--project-config-dir", value: "<string>", type: "string", description: "The directory that contains `.infisical.json`. Use it when the file isn't in the directory you run the command from, such as in a monorepo." },+ { name: "--project-config-dir", value: "<string>", type: "string", description: "The directory that contains `.infisical.yaml`. Use it when the file isn't in the directory you run the command from, such as in a monorepo." },{ name: "--projectId", value: "<string>", type: "string", description: "The project to fetch secrets from. Required when you authenticate with a machine identity. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--recursive", type: "bool", description: "Also inject the secrets in every subfolder of each `--path`." },{ name: "--secret-overriding", type: "bool", default: "true", description: "Use your personal secrets in place of shared secrets with the same name. Pass `--secret-overriding=false` to use only shared secrets." },@@ -1215,7 +1215,7 @@ infisical run --projectId=<project-id> --env=prod -- npm start` },]}>-Inject secrets from Infisical into a process as environment variables. The CLI fetches the secrets for the project linked in [`.infisical.json`](/cli/project-config), or the one you pass with `--projectId`, and starts your command with them set.+Inject secrets from Infisical into a process as environment variables. The CLI fetches the secrets for the project linked in [`.infisical.yaml`](/cli/project-config), or the one you pass with `--projectId`, and starts your command with them set.Secrets override variables that are already set in your shell. Secrets named `HOME`, `PATH`, `PS1`, `PS2`, `PWD`, `EDITOR`, `XAUTHORITY`, `USER`, `TERM`, `TERMINFO`, `SHELL`, or `MAIL`, or starting with `XDG_` or `LC_`, are never injected.@@ -1314,7 +1314,7 @@ The hook runs `infisical scan git-changes -v --staged` before each commit and blcommand="secrets"usage="[flags]"flags={[- { name: "--env", value: "<string>", type: "string", default: "dev", description: "The environment to list secrets from. Every `infisical secrets` subcommand accepts it. Defaults to the [environment set in `.infisical.json`](/cli/project-config#set-the-environment), then `dev`." },+ { name: "--env", value: "<string>", type: "string", default: "dev", description: "The environment to list secrets from. Every `infisical secrets` subcommand accepts it. Defaults to the [environment set in `.infisical.yaml`](/cli/project-config#set-the-environment), then `dev`." },{ name: "--expand", type: "bool", default: "true", description: "Resolve secret references and shell parameter expansions in secret values." },{ name: "--include-imports", type: "bool", default: "true", description: "Include secrets imported into the environment from other environments or folders." },{ name: "--output", short: "-o", value: "<string>", type: "string", description: "Print the secrets as `json`, `yaml`, or `dotenv` instead of a table." },@@ -1363,11 +1363,11 @@ For an agent on your own computer, [infisical secrets agent-proxy run](/cli/refe{ name: "--allow-readable-brokered-secrets", type: "bool", description: "Start the agent even if it can read the real value of a secret that a proxied service substitutes into its requests. Without this flag, the command exits with an error, and you fix it by removing the agent's read permission on that secret. Can also be set with `INFISICAL_AGENT_PROXY_ALLOW_READABLE_BROKERED_SECRETS`." },{ name: "--client-id", value: "<string>", type: "string", description: "The client ID of the agent's machine identity. Can also be set with `INFISICAL_UNIVERSAL_AUTH_CLIENT_ID`." },{ name: "--client-secret", value: "<string>", type: "string", description: "The client secret of the agent's machine identity. Can also be set with `INFISICAL_UNIVERSAL_AUTH_CLIENT_SECRET`." },- { name: "--env", short: "-e", value: "<string>", type: "string", required: true, description: "The environment to fetch proxied services and secrets from. Without it, the CLI reads `INFISICAL_ENVIRONMENT`, then the environment that `.infisical.json` maps to your git branch, then its `defaultEnvironment`." },+ { name: "--env", short: "-e", value: "<string>", type: "string", required: true, description: "The environment to fetch proxied services and secrets from. Without it, the CLI reads `INFISICAL_ENVIRONMENT`, then the environment that `.infisical.yaml` maps to your git branch, then its `default-environment`." },{ name: "--no-proxy", value: "<string>", type: "string", description: "More hosts for the agent to reach directly instead of through the proxy, separated by commas. Always merged with `localhost,127.0.0.1` and any `NO_PROXY` in your environment." },- { name: "--path", value: "<string>", type: "string", default: "/", description: "The folder to fetch proxied services and secrets from. Without it, the CLI reads `INFISICAL_SECRET_PATH`, then `defaultSecretPath` in `.infisical.json`." },- { name: "--projectId", value: "<string>", type: "string", required: true, description: "The project to fetch proxied services and secrets from. Can also be set with `INFISICAL_PROJECT_ID`, or read from `.infisical.json`." },- { name: "--proxy", value: "<string>", type: "string", required: true, description: "The agent proxy's address as `host:port`. Can also be set with `INFISICAL_AGENT_PROXY_ADDRESS`. It's never read from `.infisical.json`." },+ { name: "--path", value: "<string>", type: "string", default: "/", description: "The folder to fetch proxied services and secrets from. Without it, the CLI reads `INFISICAL_SECRET_PATH`, then `default-secret-path` in `.infisical.yaml`." },+ { name: "--projectId", value: "<string>", type: "string", required: true, description: "The project to fetch proxied services and secrets from. Can also be set with `INFISICAL_PROJECT_ID`, or read from `.infisical.yaml`." },+ { name: "--proxy", value: "<string>", type: "string", required: true, description: "The agent proxy's address as `host:port`. Can also be set with `INFISICAL_AGENT_PROXY_ADDRESS`. It's never read from `.infisical.yaml`." },{ name: "--token", value: "<string>", type: "string", description: "A machine identity access token to authenticate with, instead of `--client-id` and `--client-secret`. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`." },]}examples={[@@ -1398,13 +1398,13 @@ The command exits with the agent's exit code.{ name: "--allow-host", value: "<stringArray>", type: "stringArray", description: "A host the agent can reach, without a credential, when `--unmatched-host=block` is set. Repeatable." },{ name: "--allow-read", value: "<stringArray>", type: "stringArray", description: "A path the agent can read even though the sandbox blocks it by default, such as `~/.aws/config`. The path stays read-only, and the rest of a denied directory stays denied. Repeatable." },{ name: "--allow-write", value: "<stringArray>", type: "stringArray", description: "A path the agent can write, beyond the working directory, the temporary directory, and the state directories of Claude Code, Codex, and Gemini CLI. Repeatable." },- { name: "--env", short: "-e", value: "<string>", type: "string", required: true, description: "The environment to fetch proxied services from. Without it, the CLI reads `INFISICAL_ENVIRONMENT`, then the environment that `.infisical.json` maps to your git branch, then its `defaultEnvironment`." },+ { name: "--env", short: "-e", value: "<string>", type: "string", required: true, description: "The environment to fetch proxied services from. Without it, the CLI reads `INFISICAL_ENVIRONMENT`, then the environment that `.infisical.yaml` maps to your git branch, then its `default-environment`." },{ name: "--log-file", value: "<string>", type: "string", description: "A file to write the proxy's per-request activity to. The file is appended to. Without it, nothing is written, and only warnings and errors print to stderr unless you pass `--log-level`." },{ name: "--no-sandbox", type: "bool", description: "Run the agent without the OS sandbox. Credentials are still brokered, but the agent can read your files and keyring and reach the network directly." },{ name: "--pass-env", value: "<stringArray>", type: "stringArray", description: "One of your environment variables to pass through to the agent, by name, when the command would otherwise remove it. Repeatable." },- { name: "--path", value: "<string>", type: "string", default: "/", description: "The folder to fetch proxied services from. Without it, the CLI reads `INFISICAL_SECRET_PATH`, then `defaultSecretPath` in `.infisical.json`." },+ { name: "--path", value: "<string>", type: "string", default: "/", description: "The folder to fetch proxied services from. Without it, the CLI reads `INFISICAL_SECRET_PATH`, then `default-secret-path` in `.infisical.yaml`." },{ name: "--poll-interval", value: "<int>", type: "int", default: "60", description: "The number of seconds between refreshes of permissions and credentials." },- { name: "--projectId", value: "<string>", type: "string", required: true, description: "The project to fetch proxied services from. Can also be set with `INFISICAL_PROJECT_ID`, or read from `.infisical.json`." },+ { name: "--projectId", value: "<string>", type: "string", required: true, description: "The project to fetch proxied services from. Can also be set with `INFISICAL_PROJECT_ID`, or read from `.infisical.yaml`." },{ name: "--sandbox", type: "bool", default: "true", description: "Run the agent inside the OS sandbox. Pass `--sandbox=false` or `--no-sandbox` to turn it off. Can also be set with `INFISICAL_AGENT_PROXY_SANDBOX`, where `0`, `false`, or `off` turns it off." },{ name: "--set-env", value: "<stringArray>", type: "stringArray", description: "An environment variable to set in the agent, as `KEY=VALUE`. It overrides every other value. Repeatable." },{ name: "--token", value: "<string>", type: "string", description: "A token to broker with, instead of your login. Without it, the CLI reads `INFISICAL_UNIVERSAL_AUTH_ACCESS_TOKEN`, then `INFISICAL_TOKEN`, then uses your login." },@@ -1412,7 +1412,7 @@ The command exits with the agent's exit code.]}examples={[{ title: "Run an agent in the sandbox", code: "infisical secrets agent-proxy run --projectId=<project-id> --env=dev --path=/coding-agent -- claude" },- { title: "Read the project and environment from .infisical.json", code: "infisical secrets agent-proxy run -- claude" },+ { title: "Read the project and environment from .infisical.yaml", code: "infisical secrets agent-proxy run -- claude" },{ title: "Allow only proxied services and one registry", code: "infisical secrets agent-proxy run --env=dev --unmatched-host=block --allow-host=registry.npmjs.org -- claude" },{ title: "Keep a log of proxied requests", code: "infisical secrets agent-proxy run --env=dev --log-file=/tmp/agent-proxy.log -- claude" },]}@@ -1678,7 +1678,7 @@ Manage service tokens. Service tokens are deprecated and will be removed in a fu{ name: "--access-level", short: "-a", value: "<stringSlice>", type: "stringSlice", required: true, description: "What the token can do: `read`, `write`, or both. Repeat the flag or separate the values with commas." },{ name: "--expiry-seconds", short: "-e", value: "<int>", type: "int", default: "86400", description: "How long the token lasts, in seconds from now. Pass `0` for a token that never expires." },{ name: "--name", short: "-n", value: "<string>", type: "string", default: "Service token generated via CLI", description: "The token's name." },- { name: "--projectId", value: "<string>", type: "string", description: "The project to create the token for. Without it, the CLI uses the project in `.infisical.json`. Can also be set with `INFISICAL_PROJECT_ID`." },+ { name: "--projectId", value: "<string>", type: "string", description: "The project to create the token for. Without it, the CLI uses the project in `.infisical.yaml`. Can also be set with `INFISICAL_PROJECT_ID`." },{ name: "--scope", short: "-s", value: "<stringSlice>", type: "stringSlice", required: true, description: "An environment and folder the token can access, as `<env-slug>:<folder-path>`, such as `dev:/backend`. The folder path can be a glob pattern. Repeat the flag for several scopes." },{ name: "--token-only", type: "bool", description: "Print only the token, to standard output, with no other details." },]}diff --git a/docs/cli/usage.mdx b/docs/cli/usage.mdxindex 7089419196..252bc84abe 100644--- a/docs/cli/usage.mdx+++ b/docs/cli/usage.mdx@@ -58,7 +58,7 @@ If your Infisical instance is behind a service that requires its own headers, suOn Windows, `setx` saves the variable for new sessions only, so restart PowerShell before you run the next command.- To set the instance another way, such as with the `--domain` flag or in `.infisical.json`, see [Set the Infisical instance](/cli/project-config#set-the-infisical-instance).+ To set the instance another way, such as with the `--domain` flag or in `.infisical.yaml`, see [Set the Infisical instance](/cli/project-config#set-the-infisical-instance).</Step><Step>Log in with the client ID and client secret, and store the access token in the `INFISICAL_TOKEN` environment variable:diff --git a/docs/documentation/getting-started/cli.mdx b/docs/documentation/getting-started/cli.mdxindex 4a56b02067..eb6b117caf 100644--- a/docs/documentation/getting-started/cli.mdx+++ b/docs/documentation/getting-started/cli.mdx@@ -100,7 +100,7 @@ infisical login## Initialization-Navigate to the root of your project directory and run the `init` command. This step connects your local project to the project on the Infisical platform and creates a `.infisical.json` file containing a reference to that latter project.+Navigate to the root of your project directory and run the `init` command. This step connects your local project to the project on the Infisical platform and creates a `.infisical.yaml` file containing a reference to that latter project.```consoleinfisical initdiff --git a/docs/documentation/guides/local-development.mdx b/docs/documentation/guides/local-development.mdxindex 096053ebaf..fe692232bc 100644--- a/docs/documentation/guides/local-development.mdx+++ b/docs/documentation/guides/local-development.mdx@@ -117,7 +117,7 @@ The hook stops the commit when it finds something that looks like a secret. ChecThe CLI is probably reading from a different environment or folder than the one holding your secret. Run `infisical secrets --env=dev --path=/` to see what it resolves to, confirm the environment slug in your project settings, and add `--path` if the secret lives in a folder rather than at the root.</Accordion><Accordion title="The CLI can't find your project, or asks you to log in again">- The CLI is pointed at the wrong instance. It uses Infisical Cloud US by default, so an EU or self-hosted account needs the address set through the `INFISICAL_DOMAIN` environment variable, the `--domain` flag, or the `domain` field in [`.infisical.json`](/cli/project-config).+ The CLI is pointed at the wrong instance. It uses Infisical Cloud US by default, so an EU or self-hosted account needs the address set through the `INFISICAL_DOMAIN` environment variable, the `--domain` flag, or the `general.domain` field in [`.infisical.yaml`](/cli/project-config).</Accordion><Accordion title="It works in your terminal but not in your editor">Your editor's run configuration starts your application on its own, outside the `infisical run` process, and the injected variables exist only inside that process and the commands it starts. Change the run configuration to call `infisical run --env=dev -- <your-start-command>`. Avoid launching the editor itself through `infisical run`, because its extensions, language servers, and other child processes would also inherit the secrets.diff --git a/docs/documentation/guides/nextjs-vercel.mdx b/docs/documentation/guides/nextjs-vercel.mdxindex 3d95f995b2..e1fe5a6c2b 100644--- a/docs/documentation/guides/nextjs-vercel.mdx+++ b/docs/documentation/guides/nextjs-vercel.mdx@@ -161,7 +161,7 @@ infisical login### Initialization-Run the `init` command at the root of the Next.js app. This step connects your local project to the project on the Infisical platform and creates a `.infisical.json` file containing a reference to that latter project.+Run the `init` command at the root of the Next.js app. This step connects your local project to the project on the Infisical platform and creates a `.infisical.yaml` file containing a reference to that latter project.```consoleinfisical initdiff --git a/docs/documentation/platform/agent-proxy/local-agent-proxy.mdx b/docs/documentation/platform/agent-proxy/local-agent-proxy.mdxindex 910496c0d7..2cb7d8fce6 100644--- a/docs/documentation/platform/agent-proxy/local-agent-proxy.mdx+++ b/docs/documentation/platform/agent-proxy/local-agent-proxy.mdx@@ -97,14 +97,14 @@ See [Platform support](#platform-support) for what happens where the sandbox is## Running an agent-Every option resolves the same way: **the flag → an environment variable → `.infisical.json` → the default.** Run it from a directory that has an `.infisical.json` (created by `infisical init`) and the project, environment, and path come from there, so most of the flags fall away:+Every option resolves the same way: **the flag → an environment variable → `.infisical.yaml` → the default.** Run it from a directory that has an `.infisical.yaml` (created by `infisical init`) and the project, environment, and path come from there, so most of the flags fall away:-| Option | Flag | Environment variable | `.infisical.json` |+| Option | Flag | Environment variable | `.infisical.yaml` || --- | --- | --- | --- |-| Project | `--projectId` | `INFISICAL_PROJECT_ID` | `workspaceId` |-| Environment slug | `--env` | `INFISICAL_ENVIRONMENT` | `defaultEnvironment` |-| Secret path | `--path` | `INFISICAL_SECRET_PATH` | `defaultSecretPath` |-| Instance | `--domain` | `INFISICAL_DOMAIN` | `domain` |+| Project | `--projectId` | `INFISICAL_PROJECT_ID` | `secrets-management.project-id` |+| Environment slug | `--env` | `INFISICAL_ENVIRONMENT` | `secrets-management.default-environment` |+| Secret path | `--path` | `INFISICAL_SECRET_PATH` | `secrets-management.default-secret-path` |+| Instance | `--domain` | `INFISICAL_DOMAIN` | `general.domain` || Sandbox | `--sandbox` / `--no-sandbox` | `INFISICAL_AGENT_PROXY_SANDBOX` | — |Everything after `--` is your agent's own command, run as-is. From a project directory:@@ -361,7 +361,7 @@ infisical secrets agent-proxy run -e dev --no-sandbox -- claudeBrokering still works and the environment is still scrubbed, but the agent is uncontained: it can read your keyring and credential files and reach the network directly, bypassing the proxy. `run` prints a warning saying so. This is a debugging tool, and the only option on Windows.-`INFISICAL_AGENT_PROXY_SANDBOX=0` does the same thing. Neither can be set from `.infisical.json`, deliberately, so a committed file can't quietly disable the boundary for everyone who runs the agent.+`INFISICAL_AGENT_PROXY_SANDBOX=0` does the same thing. Neither can be set from `.infisical.yaml`, deliberately, so a committed file can't quietly disable the boundary for everyone who runs the agent.## Next stepsdiff --git a/docs/documentation/platform/agent-proxy/quickstart/local-proxy.mdx b/docs/documentation/platform/agent-proxy/quickstart/local-proxy.mdxindex 156bf76891..07b261f984 100644--- a/docs/documentation/platform/agent-proxy/quickstart/local-proxy.mdx+++ b/docs/documentation/platform/agent-proxy/quickstart/local-proxy.mdx@@ -80,7 +80,7 @@ infisical secrets agent-proxy run --projectId=<project-id> --env=dev --path=/codThis one command starts the proxy and your agent together, and shuts the proxy down when the agent exits. The agent behaves exactly as if you had launched it directly. In its environment it finds `GITHUB_TOKEN`, set to the fake `ghp_…` placeholder, and uses it like a normal token. Calls to `api.github.com` get the real token swapped in as they pass through; everything else goes out untouched. Meanwhile the agent is sandboxed: it can't read your keyring, your `~/.aws` or `~/.ssh`, or your Infisical token.<Note>- In a directory with an `.infisical.json` (from `infisical init`) you can drop `--projectId`. `--env` and `--path` fall back to environment variables too, so in a configured shell this is just `agent-proxy run -- claude`.+ In a directory with an `.infisical.yaml` (from `infisical init`) you can drop `--projectId`. `--env` and `--path` fall back to environment variables too, so in a configured shell this is just `agent-proxy run -- claude`.</Note><Note>diff --git a/docs/documentation/platform/agent-proxy/standalone-agent-proxy.mdx b/docs/documentation/platform/agent-proxy/standalone-agent-proxy.mdxindex cde933fddd..41459703d3 100644--- a/docs/documentation/platform/agent-proxy/standalone-agent-proxy.mdx+++ b/docs/documentation/platform/agent-proxy/standalone-agent-proxy.mdx@@ -62,19 +62,19 @@ Each authenticates as its own [machine identity](/documentation/platform/identit## Configuration-Every option resolves from the same sources, in order: **the flag → an environment variable → `.infisical.json` → the built-in default.** An explicitly-passed flag always wins. Where the environment variables are already set on the host, the flags fall away and only your agent command remains: `infisical secrets agent-proxy connect -- claude`.+Every option resolves from the same sources, in order: **the flag → an environment variable → `.infisical.yaml` → the built-in default.** An explicitly-passed flag always wins. Where the environment variables are already set on the host, the flags fall away and only your agent command remains: `infisical secrets agent-proxy connect -- claude`.-| Option | Flag | Environment variable | `.infisical.json` |+| Option | Flag | Environment variable | `.infisical.yaml` || --- | --- | --- | --- || Auth | `--client-id` / `--client-secret` | `INFISICAL_UNIVERSAL_AUTH_CLIENT_ID` / `_SECRET` | — |-| Instance | `--domain` | `INFISICAL_DOMAIN` | `domain` |-| Project | `--projectId` | `INFISICAL_PROJECT_ID` | `workspaceId` |-| Environment slug | `--env` | `INFISICAL_ENVIRONMENT` | `defaultEnvironment` |-| Secret path | `--path` | `INFISICAL_SECRET_PATH` | `defaultSecretPath` |+| Instance | `--domain` | `INFISICAL_DOMAIN` | `general.domain` |+| Project | `--projectId` | `INFISICAL_PROJECT_ID` | `secrets-management.project-id` |+| Environment slug | `--env` | `INFISICAL_ENVIRONMENT` | `secrets-management.default-environment` |+| Secret path | `--path` | `INFISICAL_SECRET_PATH` | `secrets-management.default-secret-path` || Proxy address | `--proxy` | `INFISICAL_AGENT_PROXY_ADDRESS` | — |<Note>- The proxy address is the one setting that can't come from `.infisical.json`. That file is usually committed to your repository, so a wrong or malicious value would silently route every agent's traffic through the wrong host. Pass it with `--proxy` or `INFISICAL_AGENT_PROXY_ADDRESS` instead.+ The proxy address is the one setting that can't come from `.infisical.yaml`. That file is usually committed to your repository, so a wrong or malicious value would silently route every agent's traffic through the wrong host. Pass it with `--proxy` or `INFISICAL_AGENT_PROXY_ADDRESS` instead.</Note>See the [CLI reference](/cli/reference#secrets-agent-proxy) for every flag on both subcommands.diff --git a/docs/snippets/cli/local-development/link-project.mdx b/docs/snippets/cli/local-development/link-project.mdxindex 4597ddc887..bd8017fec6 100644--- a/docs/snippets/cli/local-development/link-project.mdx+++ b/docs/snippets/cli/local-development/link-project.mdx@@ -5,8 +5,8 @@ cd /path/to/your/projectinfisical init```-Select your organization and project when prompted. This creates an `.infisical.json` file with your [local project settings](/cli/project-config), so the commands you run next don't need a project ID.+Select your organization and project when prompted. This creates an `.infisical.yaml` file with your [local project settings](/cli/project-config), so the commands you run next don't need a project ID.<Note>- `.infisical.json` holds no secret values, so you can safely commit it to version control. Everyone who clones the repository is then pointed at the same project.+ `.infisical.yaml` holds no secret values, so you can safely commit it to version control. Everyone who clones the repository is then pointed at the same project.</Note>