Feast CLI reference
Overview
The Feast CLI comes bundled with the Feast Python package. It is immediately available after installing Feast.
Usage: feast [OPTIONS] COMMAND [ARGS]...
Feast CLI
For more information, see our public docs at https://docs.feast.dev/
Options:
-c, --chdir TEXT Switch to a different feature repository directory before
executing the given subcommand.
--help Show this message and exit.
Commands:
apply Create or update a feature store deployment
configuration Display Feast configuration
entities Access entities
feature-views Access feature views
init Create a new Feast repository
materialize Run a (non-incremental) materialization job to...
materialize-incremental Run an incremental materialization job to ingest...
permissions Access permissions
registry-dump Print contents of the metadata registry
teardown Tear down deployed feature store infrastructure
version Display Feast SDK versionGlobal Options
The Feast CLI provides one global top-level option that can be used with other commands
chdir (-c, --chdir)
This command allows users to run Feast CLI commands in a different folder from the current working directory.
Apply
Creates or updates a feature store deployment
What does Feast apply do?
Feast will scan Python files in your feature repository and find all Feast object definitions, such as feature views, entities, and data sources.
Feast will validate your feature definitions (e.g. for uniqueness of features)
Feast will sync the metadata about Feast objects to the registry. If a registry does not exist, then it will be instantiated. The standard registry is a simple protobuf binary file that is stored on disk (locally or in an object store).
Feast CLI will create all necessary feature store infrastructure. The exact infrastructure that is deployed or configured depends on the
providerconfiguration that you have set infeature_store.yaml. For example, settinglocalas your provider will result in asqliteonline store being created.
feast apply (when configured to use cloud provider like gcp or aws) will create cloud infrastructure. This may incur costs.
Configuration
Display the actual configuration being used by Feast, including both user-provided configurations and default configurations applied by Feast.
Entities
List all registered entities
Feature views
List all registered feature views
Init
Creates a new feature repository
It's also possible to use other templates
or to set the name of the new project
Materialize
Load data from feature views into the online store between two dates
Load data for specific feature views into the online store between two dates
Materialize incremental
Load data from feature views into the online store, beginning from either the previous materialize or materialize-incremental end date, or the beginning of time.
Permissions
List permissions
List all registered permission
verbose option describes the resources matching each configured permission:
Describe a permission
Describes the provided permission
Permission check
The permissions check command is used to identify resources that lack the appropriate permissions based on their type, name, or tags.
This command is particularly useful for administrators when roles, actions, or permissions have been modified or newly configured. By running this command, administrators can easily verify which resources and actions are not protected by any permission configuration, ensuring that proper security measures are in place.
List of the configured roles
List all the configured roles
verbose option describes the resources and actions permitted to each managed role:
Teardown
Tear down deployed feature store infrastructure
Version
Print the current Feast version
Last updated
Was this helpful?