📄️ What Does Deploying a Catalog Do?
When you deploy a catalog in AtScale, all of its the models and perspectives become available for queries. After a model is deployed, it can be accessed by your business intelligence (BI) client applications.
📄️ Deploying a Catalog
Deploying a catalog deploys all of the models in the repository so they can be accessed and queried from BI tools.
📄️ Configuring Permissions on Deployed Models
You can configure runtime permissions on deployed models and perspectives to control which users can access them from BI tools. These permissions can be set at the user or group level.
📄️ Configuring Resource Permissions for Deployed Models
Resource permissions enable you to control which users and groups can access resources (such as metrics and calculations) in your deployed models from BI tools. This gives you finer-grained control over access to your model data than model permissions, which apply to the entire model.
📄️ Undeploying Catalogs
Undeploying a catalog removes it and its models from AtScale's runtime environment. Client connections and queries can no longer access the models in the catalog. You can only undeploy an entire catalog, not its individual models.
📄️ Known Issues and Limitations
6400 deployed semantic object limit