Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.prophecy.ai/llms.txt

Use this file to discover all available pages before exploring further.

Publication lets you create reusable project versions and deploy those versions to development or production environments Publication applies only to SQL projects that use Simple Version Control.

​
Publication workflow

Prophecy separates publication into three stages:
StagePurpose
Save a draftSave work in progress
Publish a project versionCreate a reusable version of the project
DeployMake that version available in a specific environment
Publishing does not automatically run pipelines. After deployment, you can schedule pipelines independently for each fabric.

​
Save a draft

As you develop and edit your project, you can save drafts to store in-progress project changes before publication. Use drafts to:
  • Save work while continuing development.
  • Collaborate with other users.
  • Review changes before publication.
  • Prepare a version for deployment.
Saving a draft does not create a deployable project version and does not make changes available in deployment environments.

​
Publish a version

Publishing creates a reusable version of the project, but does not automatically deploy it to your Databricks, Snowflake, or BigQuery environment. Until deployment occurs, the published version remains available in Prophecy but is not yet available in a development or production environment. When you publish a version, Prophecy:
  • Assigns a version number and description.
  • Packages the project.
  • Makes the version available for deployment.
Published versions are immutable, meaning that once you publish a version, Prophecy preserves it as a stable reference for deployment and rollback. This helps you:
  • Track project changes over time.
  • Deploy consistent versions across environments.
  • Roll back to earlier project versions if necessary.

​
Deploy a project

When you deploy a project, you make a published version available in a specific deployment environment. In Prophecy, deployment environments are called fabrics. Examples include development, staging, and production environments for platforms such as Databricks, Snowflake, or BigQuery. Different environments often require different configurations, such as connections, schemas, or runtime parameters. You can use project parameter sets to apply environment-specific configuration during deploymen During deployment, Prophecy:
  • Builds the project in the selected environment.
  • Applies the selected project parameter set.
  • Creates or updates the deployment for that environment.
You can deploy different versions of the same project to different environments. For example, a development environment might use version 1.1 while production continues using version 1.0. However, an environment can contain only one deployed version of a project at a time. After deployment, you can schedule pipelines independently for each environment.