Got it — after a reset, your workspace won’t have any block types registered. In Prefect 3.x, you register block types with the CLI so they become available in the UI, then optionally create configured block instances. Here’s the quickest way to get local filesystem, credential, and all GCP-related blocks visible: 1) Install the GCP integration (needed for GCP blocks)

pip install "prefect[gcp]"  # or: pip install prefect-gcp

2) Register core Prefect block types - Local filesystem blocks:

prefect block register -m prefect.filesystems

- Core credential/secret block:

prefect block register -m prefect.blocks.system

3) Register GCP block types

prefect block register -m prefect_gcp.credentials
prefect block register -m prefect_gcp.cloud_storage
prefect block register -m prefect_gcp.bigquery
prefect block register -m prefect_gcp.secret_manager

Notes - Using specific submodules (like

prefect_gcp.cloud_storage

) is the reliable approach;

prefect block register

does not automatically recurse into all submodules of

prefect_gcp

. - You can re-run registration safely; it updates existing block type definitions if they change. - Make sure your CLI is pointed at the same API/workspace as your UI (e.g., Prefect Cloud workspace or your local server). You can verify with

prefect config view

and by checking

PREFECT_API_URL

. Verify and create instances (optional) - See which block types are available:

prefect block type ls

- Create a configured block instance in the UI or via CLI, e.g.:

prefect block create gcs-bucket
prefect block create gcp-credentials
prefect block create local-file-system
prefect block create secret

This will open a link to the UI to finish configuration. Docs - CLI: prefect block CLI reference - Blocks overview: Blocks concept - GCP integration: Prefect GCP integration If you want me to script this as a one-shot setup for your environment, tell me how you’re running Prefect (local server vs Cloud) and I’ll tailor the commands.

Short answer: there isn’t a built-in “register everything” command in Prefect 3.x. You must register modules that define Block types. If you want a simple, “register all blocks I’m likely to have installed” script for local Prefect, use this. It registers core blocks and then tries common integration submodules, only registering ones that are importable on your machine (ignores the rest):

# Core Prefect blocks
prefect block register -m prefect.filesystems || true
prefect block register -m prefect.blocks.system || true
prefect block register -m prefect.blocks.notifications || true

# Try popular integration block modules if installed (GCP, AWS, Azure, Snowflake)
mods="
prefect_gcp.credentials
prefect_gcp.cloud_storage
prefect_gcp.bigquery
prefect_gcp.secret_manager
prefect_aws.credentials
prefect_aws.s3
prefect_aws.secrets_manager
prefect_aws.lambda_function
prefect_aws.glue_job
prefect_azure.credentials
prefect_azure.blob_storage
prefect_azure.key_vault
prefect_snowflake.credentials
prefect_snowflake.database
"

for m in $mods; do
  python - <<PY
import importlib, subprocess, sys
m = "$m"
try:
    importlib.import_module(m)
except Exception:
    sys.exit(2)
subprocess.run(["prefect", "block", "register", "-m", m], check=False)
PY
done

# See what’s available now
prefect block type ls

Notes - Install any integrations you want before running this (e.g.,

pip install "prefect[gcp]"

,

pip install "prefect[aws]"

, etc.). - The loop is safe to re-run; it updates existing block type definitions if needed. - This targets common modules where blocks are defined (e.g.,

prefect_gcp.cloud_storage

,

prefect_aws.s3

). Some packages expose blocks at submodules rather than the top-level package. - Make sure your CLI points at the same API/workspace your UI is connected to. Docs: prefect block CLI reference