To use SaaS Runtime, you need a repository in Artifact Registry to store the blueprint.
The blueprint defines the SaaS application and infrastructure that you deploy with SaaS Runtime. For more details about blueprints, see Blueprints in SaaS Runtime.
Before you begin
Ensure you have enabled SaaS Runtime.
Creating a repository
To create the repository, review the following details specific to SaaS Runtime. Then, follow the instructions to create standard repositories in the Artifact Registry documentation.
Details about repositories for SaaS Runtime
As you set up a repository in Artifact Registry, take into account the following details:
When you configure the repository details:
- For Format, select Docker. Even though we're storing Terraform configurations, SaaS Runtime uses the OCI (Open Container Initiative) image format to package the Terraform configurations. OCI images are compatible with Docker tooling.
- For mode, select standard.
For the region of the repository, you can choose any region that is supported by Artifact Registry. This region does not need to match the regions where SaaS Runtime provisions the SaaS application and infrastructure.
However, if you plan to use Cloud Build in the same Google Cloud project to build and push blueprints, it can be helpful to choose the same region for your Cloud Build jobs, Artifact Registry repository and Developer Connect.
What's next
- Try the quickstart to get started using SaaS Runtime.
- Learn more about the blueprints that define the SaaS application and infrastructure.
- To learn more about SaaS Runtime, see SaaS Runtime Overview.