pull
prefect.deployments.steps.pull
Core set of steps for specifying a Prefect project pull step.
Functions
set_working_directory
Sets the working directory; works with both absolute and relative paths.
Args:
directory
: the directory to set as the working directory
Returns:
- a dictionary containing a
directory
key of the directory that was set
git_clone
Clones a git repository into the current working directory.
Args:
repository
: the URL of the repository to clonebranch
: the branch to clone; if not provided, the default branch will be usedcommit_sha
: the commit SHA to clone; if not provided, the default branch will be usedinclude_submodules
: whether to include git submodules when cloning the repositoryaccess_token
: an access token to use for cloning the repository; if not provided the repository will be cloned using the default git credentialscredentials
: a GitHubCredentials, GitLabCredentials, or BitBucketCredentials block can be used to specify the credentials to use for cloning the repository.directories
: Specify directories you want to be included (uses git sparse-checkout)
Returns:
- a dictionary containing a
directory
key of the new directory that was created
Raises:
subprocess.CalledProcessError
: if the git clone command fails for any reason
Examples:
Clone a public repository:
Clone a branch of a public repository:
Clone a private repository using a GitHubCredentials block:
Clone a private repository using an access token:
Note that you will need to create a Secret block to store the
value of your git credentials. You can also store a username/password combo or token prefix (e.g. x-token-auth
)
in your secret block. Refer to your git providers documentation for the correct authentication schema.
Clone a repository with submodules:
Clone a repository with an SSH key (note that the SSH key must be added to the worker before executing flows):
Clone a repository using sparse-checkout (allows specific folders of the repository to be checked out)