# Installer faas-cli avec Homebrew, chocolatey, Nix, scoop Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de faas-cli pour les workflows d'agents IA. ## installation ```sh sudo av install brew:faas-cli ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install faas-cli ``` Preuve: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#faas-cli ``` Preuve: nixpkgs package indexes: pkgs/by-name/fa/faas-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Chocolatey (92%): ```sh choco install faas-cli ``` Preuve: Chocolatey community package catalog: faas-cli from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='10.102','registrychangesview' - Scoop (92%): ```sh scoop install main/faas-cli ``` Preuve: Scoop official bucket manifest trees: bucket/faas-cli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Faits du paquet - **Clé du paquet:** brew:faas-cli - **Gestionnaire de paquets:** Homebrew - **Version:** 0.18.12 - **Résumé source:** CLI for templating and/or deploying FaaS functions - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-07-27T12:27:17Z - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - faas (alias) - faas-cli (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.18.12 ## Historique du projet et usages faas-cli is the official command-line interface for OpenFaaS, used to create, build, push, deploy, invoke, and manage serverless functions. ### Historique du projet The faas-cli repository was created in April 2017 as the OpenFaaS command-line entry point. The project README describes it as the official CLI for OpenFaaS and explains the original core workflow: write a handler, pick a language template, and let the CLI build a Docker image and deploy the function. As OpenFaaS matured, faas-cli became the stable user-facing tool around a broader platform. Its command set grew from the basic new, build, push, deploy, remove, and invoke lifecycle into template stores, secrets, registry login, multi-arch publishing, and OpenFaaS Pro authentication flows. The CLI also reflects OpenFaaS's packaging strategy. Official installation docs support a curl installer, Homebrew, Windows binaries, Chocolatey, Scoop, and direct release downloads, so the same tool fits local demos, CI pipelines, and workstation use. ### Historique d'adoption OpenFaaS adoption made faas-cli important because nearly every getting-started path goes through it. The README shows Homebrew installation, a `faas` alias, and commands for creating functions from templates, while the official install docs document cross-platform packaging for macOS, Linux, and Windows. The CLI's adoption is tied to the OpenFaaS gateway model: developers log in to a gateway, point the CLI at `OPENFAAS_URL` or a gateway flag, then deploy function definitions from YAML. That made it a bridge between local source trees, Docker registries, and Kubernetes or other OpenFaaS providers. ### Modes d'utilisation Typical use starts with `faas-cli new` to scaffold a function from a language template, then `faas-cli up` as the shorthand for build, push, and deploy. Operators use `faas-cli login`, `secret`, `store`, `invoke`, `remove`, and gateway flags or environment variables to work with local or remote OpenFaaS installations. The CLI is also a packaging surface for templates. Official docs describe pulling templates from remote Git repositories and using a template store for official, incubator, and community templates, which is why the tool matters beyond simply sending API calls to a gateway. ### Pourquoi les passionnés de paquets s'y intéressent For package people, faas-cli is a clean example of a Go-based cloud CLI distributed through many channels while keeping a curl installer and release binaries as the canonical path. It also carries the familiar package-manager tension noted by its README: Homebrew is updated regularly, but may not always be the newest minor release. Its command alias matters too. Installing the package gives both `faas-cli` and `faas`, which is the sort of executable naming detail that package formulas, shell completions, and docs all have to keep aligned. ### Chronologie - 2017: The faas-cli repository is created as the OpenFaaS CLI. - 2020: The CLI includes release entries for list output improvements and gateway/provider serialization updates. - 2021: Release entries add registry-login and secrets whitespace handling. - 2026: The README continues to document core build, deploy, template, secret, publish, and Pro auth commands. ### Related projects - OpenFaaS is the serverless platform that faas-cli targets. - openfaas/templates provides the default language templates used by `faas-cli new` and `faas-cli template pull`. ### Sources - - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Credential files - Unix: ~/.openfaas/config.yml, .openfaas/config.yml ## Autres enregistrements de gestionnaires de paquets - Nix - faas-cli: normalized package name match | nixpkgs package indexes: pkgs/by-name/fa/faas-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Chocolatey - faas-cli: normalized package name match | Chocolatey community package catalog: faas-cli from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='10.102','registrychangesview' - Scoop - main/faas-cli: normalized package name match | Scoop official bucket manifest trees: bucket/faas-cli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/faas-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/faas-cli.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph