@Marvin What is the difference between a BLOCK document and a BLOCK schema?

Based on the fetched documents: ### BLOCK Document: - How Blocks are Created: Blocks can be created via code or through the UI. - Example: For instance, creating a dbt Cloud Credentials block involves: - Logging into your dbt Cloud account. - Copying the API Key and account details. - Running specific Prefect code snippets to save the block with the credentials. ### BLOCK Schema: - Definition: A schema is a structured dataset that Prefect can use within Blocks. - Components: For example, dbt CLI TargetConfigs schema includes details like the number of threads for dbt operations. - Usage: Schemas define useful configurations and structures that can be loaded and used in Prefect workflows. In essence: - BLOCK Document: Represents a complete Block entity, typically encompassing configurations or credentials. - BLOCK Schema: Defines the structure or layout (schema) of the data set used within Blocks. For further details, refer to the documentation linked within the explanations.

hi @Chris Sankat a block document you could imagine as the dictionary that is produced if you did

MyBlock().dict()

(using pydantic 1 syntax), there's a table for individual block documents in the db the schema is more or less what you get if you did

MyBlock.schema()

(again, v1 syntax) - again, there's an independent table for these in the db does that answer your question? we need to keep these things separate to allow you to change

MyBlock

implementation without breaking all your existing documents entirely