vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Sample solutions for IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-sol-overview).







 April 2021 

Review the release notes for April 2021.



 14 April 2021 

Ansible support in IBM Cloud Schematics is now generally available
: Use Schematics Actions to run your Ansible playbooks in IBM Cloud, and automate the configuration, operation, and management of cloud resources, or deploy multitiered app workloads. To get started, see [Schematics landing page](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started), try out one of the [IBM-provided Ansible playbooks](https://cloud.ibm.com/docs/schematics?topic=schematics-sample_actiontemplates) or learn more about how Schematics integrates Ansible in [About IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-how-it-workshow-to-actions).







 March 2021 

Review the release notes for March 2021.



 29 March 2021 

Terraform v0.14 support
: IBM Cloud Schematics now supports Terraform v0.14 now. You can now select to run your infrastructure code with Terraform version 0.11 or 0.12 or 0.13 or 0.14. Make sure that you use the syntax that is compatible with the Terraform version that you want to use. Terraform v0.14 introduced new sensitive attribute in the variable metadata configuration. Schematics do not detect this sensitive attribute. Users should continue to use the sensitive checkbox in the IBM Cloud Schematics console, and use secure flag in the API payload. Schematics already supports masking the sensitive updated values. Terraform v0.14 introduced a lock file for versions with the name .terraform.lock.hcl. This file is created during terraform init.
[Using Terraform on IBM Cloud to manage your own Red Hat OpenShift Container Platform on IBM Cloud classic infrastructure](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-redhat)Using Terraform on IBM Cloud to manage your own Red Hat OpenShift Container Platform on IBM Cloud classic infrastructure

Use this tutorial to create your own highly available Red Hat® OpenShift Container Platform 3.11 environment on IBM® Cloud classic infrastructure by using Terraform on IBM Cloud.

Red Hat OpenShift on IBM Cloud Terraform on IBM Cloud



* 3 hours
* 2023-03-07



[Setting up continuous deployment with Schematics and DevOps toolchain](https://cloud.ibm.com/docs/schematics?topic=schematics-workspace-continuous-deployment)Setting up continuous deployment with Schematics and DevOps toolchain

The ibm_cos_bucket example creates an instance of IBM Cloud Object Storage, IBM Cloud® Activity Tracker, and IBM Cloud® Monitoring.

Schematics



* 60 minutes
* 2023-03-15



[Deploying a Schematics blueprint using the command line](https://cloud.ibm.com/docs/schematics?topic=schematics-deploy-schematics-blueprint-cli)Deploying a Schematics blueprint using the command line

Use an IBM® provided sample to deploy a scalable multi-module Schematics blueprint template from the command line.

Schematics



* 30 minutes
* 2022-11-24



[Importing Schematics templates into the IBM Cloud catalog](https://cloud.ibm.com/docs/schematics?topic=schematics-private-catalog)Importing Schematics templates into the IBM Cloud catalog

Understand how to Create your private catalog, manage your private catalog, assign access to the private catalog in IBM Cloud®. And import your Terraform templates as products to make them available to your users. With a private catalog, you can limit the services that you want your users to see and the service settings that they can adjust.
Monitoring Schematics services by using IBM Cloud Monitoring 

[IBM Cloud® Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started) is a Third party cloud native, and container intelligence management system that you can include as part of your IBM Cloud Schematics. Use it to gain operational visibility into the performance and health check of your applications, services, and platforms. It offers administrators, developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

You need to create Sysdig monitor in us-south region to view the Schematics metrics that relates to workspaces, actions, or an environment that you create in US region. And create Sysdig monitor in eu-de region to view the Schematics metrics that relates to workspaces, actions, or an environment that you create in EU region.



 Launching Monitoring UI from the IBM Cloud 

You can monitor your services instance in the IBM Cloud console.

Complete these steps to view your services instances:



1. Log in to your [IBM Cloud](https://cloud.ibm.com) account by using your credentials.
2. From the IBM Cloud page, select Navigation menu > Observability > Monitoring.
3. Click your instance to view the workspace and action that you created.

For more information about how to create a service instance? see [Create service instance](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instancescreate-instance).
4. Click the Open dashboard link, and expand IBM to view the IBM Schematics Summary Counts and IBM Schematics Summary Charts dashboard list.



* Use the IBM Schematics Summary Counts dashboard to monitor the counts of your workspace state, action, and its success and failure status.
* Use the IBM Schematics Summary Charts dashboard to monitor the charts of your workspace by state, by type and outcome, and the vulnerability count.









 Creating service instance 

You can create your services instance in the IBM Cloud console.

Complete these steps to create your services instance:



1.
Estimating architecture costs in a project 

Cost estimation is available for deployable architectures in the IBM Cloud catalog. Depending on the deployable architecture, a starting cost is estimated based on the available data. This estimate is meant to be a starting point to help you determine how much your account could be charged for deploying an architecture. This estimated amount is subject to change as the architecture is customized within a project, and it does not include all resources, usage, licenses, fees, discounts, or taxes.



  Viewing the starting cost for your deployable architecture 

Depending on the deployable architecture that you select from the catalog, there is an estimated starting cost.

To view the estimated starting cost, complete the following steps:



1.  Go to the catalog details page for the deployable architecture.
2.  Next, click the Starting at amount for additional details about the cost summary.



After you add the deployable architecture to your project, you can configure the input values. By doing so, you can tailor the architecture to match your needs. Adjusting the configuration input might adjust the estimated cost.



1.  Go to the Projects page, and select a project.
2.  Go to Configurations, and select a configuration of the deployable architecture.
3.  Enter the input values to configure the deployable architecture, and click Save. For more information about configuring and deploying, see [Configuring and deploying a deployable architecture](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-config-project).
4.  After saving, the validation checks are run and a new cost estimate is computed. This might take a few minutes. After the validation is complete, you can view the estimated cost for the configured architecture on the validation modal in the Cost estimate successful section.



This estimated amount is subject to change as the architecture is customized and deployed, and it does not include all resources, usage, licenses, fees, discounts, or taxes.
If you provided your Terraform template by uploading a tape archive file (.tar), you must use the [ibmcloud schematics workspace upload](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-upload) command to provide a new version of your template.
4. Optional: Review the variables that you set for your workspace. The values of your variables are used every time that you reference the variable in your Terraform template. Make sure that your variables use the correct values.
5. Click Generate plan to create a Terraform execution plan. This action equals the terraform plan command. After you click this button, the workspace Activity page opens and Schematics starts to compare the state of the resources that you already provisioned in your IBM Cloud account with the resources that you want to provision with your Terraform template.
6. Click View log to review the log files of your execution plan. The execution plan includes a summary of IBM Cloud resources that must be created, modified, or deleted to achieve the state that you described in your Terraform template. If you have syntax errors in your Terraform configuration files, you can review the error message in the log file.
7. Review available service plans and pricing information for each of the IBM Cloud resources that Schematics is about to create or change. Some services come with a limit per IBM Cloud account. If you are about to reach the service limit for your account, the resource is not provisioned until you increase the service quota, or remove existing services first.
8. When you are ready, apply your Terraform template by clicking Apply plan. This action equals the terraform apply command. After you click the button, IBM Cloud Schematics starts provisioning, modifying, or deleting your IBM Cloud resources based on what actions were identified in the execution plan. Depending on the type and number of resources that you want to provision or modify, this process might take couple of minutes, or even up to hours to complete. During this time, you cannot make changes to your workspace.
![onboardtoibmcatalog.png](https://cloud.ibm.com/docs-content/v1/content/4cd6263f39a034d265ddb4b0a5e6d50c55d13ee8/ibm-cloud-provider-for-terraform/images/onboardtoibmcatalog.png)[onboard Terraform template to private catalog](https://cloud.ibm.com/schematics/actions/create?name=myprivatecatalogaction&url=https://github.com/Cloud-Schematics/onboard-to-ibm-catalog)







 Code snippets 

The code snippets provides the templates that you can use to understand how to configure IBM Cloud service. You can also use the snippets as a starting point for your custom templates.



* [API Gateway](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templateapi-gwy-snippet)
* [Certificate Manager](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatecert-mgr-snippet)
* [Cloud Databases templates](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatecloud-db-snippet)
* [Cloud Foundry](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatecloud-foundry-snippet)
* [Direct Link](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatedl-snippet)
Schematics blueprints is a [beta feature](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitations) that is available for evaluation and testing purposes. It is not intended for production usage. Refer to the list of [limitations](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitations) for the beta release.



 Deploying a Schematics blueprint using the command line 

Use an IBM® provided sample to deploy a scalable multi-module Schematics blueprint template from the command line.

In this tutorial, you deploy a Schematics blueprint using the Schematics command line. The tutorial demonstrates the blueprints lifecycle of creating cloud resources with a blueprint-managed cloud environment in Schematics, through to deleting the environment.

Before your begin



* Install and login to the [IBM Cloud command line](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-cli).
* Select the IBM Cloud region that you want to use to manage your Schematics blueprint environment. Set the region by running the command ibmcloud target -r <us-south>.
* Install the [Schematics command-line](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin) plug-in, or [update the command line plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-clischematics-cli-update) to access the Schematics blueprints commands.
* Check that you have the right [permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-accessblueprint-permissions) to create blueprints.





 Step 1: Select a blueprint template
* Future: scheduled ops, drift detection, cost estimation, policy compliance









 Next steps 

So far you have learned a little about Schematics Blueprints. The following are some next steps to explore.



* [Working with blueprints and environments](https://cloud.ibm.com/docs/schematics?topic=schematics-work-with-blueprints) to understand how to use blueprints to manage the lifecycle of deploying and managing cloud environments.
* See [understanding blueprint templates and configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templates) to dig into how to define cloud environments using blueprint templates and inputs of latest version.
* [Beta code for Schematics Blueprints](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitations) to provide your feedback and understand beta limitations.
Beta code for Schematics Blueprints 

The Schematics Blueprints level of code is considered beta code as and when the changes in function and capabilities between now, and the General Availability (GA) date.

Join the beta program, post a question in the [IBM Cloud Schematics users Slack](https://ibm-argonauts.slack.com/archives/CLKR4FE90), and engage with the Schematics team. If you do not have access to this Slack, [request an invitation to this Slack](https://cloud.ibm.com/schematics/slack).

Join the schematics-users slack channel and post a message include the following information.



* Your name
* email address
* Your Company or Organization name
* Your level of experience with cloud automation, specifically regarding Terraform, or IBM Cloud Schematics
* Any initial questions or comments



You can come back anytime to your created thread to add information, ask questions, or give feedback.



 Beta changes October 2022 

Blueprint commands have been renamed with the 1.12.3 release of the Schematics CLI Plugin



* blueprint create > blueprint create
* blueprint update > blueprint update
* blueprint delete > blueprint delete
* blueprint apply > blueprint apply
* blueprint destroy > blueprint destroy







 Beta release limitations 



Beta release limitations

 Limitation Resolved Date 

 Default values Planned for December 2022 Delivered Dec 2022 
 Large input value sizes up to Terraform limit of 4MB Planned for December 2022 
 Local values Local support planned for 2023 
 Input value operators, for example: merge, concatenate Planned for a 2023 release 
 Performance optimization - Parallel job execution for plan and apply Concurrent module jobs planned for 2023 release 
 Performance optimization - Plan and Apply only run against changed modules Planned for 2023 release 
 Blueprint operations are only supported by using the IBM Cloud CLI plug-in. UI support planned for December 2022 Delivered Dec 2022 
 The Terraform Plan (all) operation for blueprint template. Support planned for December 2022 
 Run operations are performed as a single operation against all modules (plan + apply).
At any particular time, a maximum of n API requests are processed by the Schematics engine. By default, n equals 20, but this number is manually adjusted by the Schematics operator based on the current API workload.

For every queued request from a Schematics user, the Schematics engine creates a dedicated runtime job that runs to completion. The request is removed from the queue when it is fully processed. The Schematics jobs are not shared between tenants or reused later.





 How is the information in IBM Cloudant and IBM Cloud Object Storage isolated from other tenant data? 

Schematics does not store any personally identifiable information. Sensitive technical information for a workspace is stored as described in [What technical information is stored in Schematics?](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-datati-data). Data that is stored in Cloudant and IBM Cloud Object Storage is encrypted in transit using TLS and at rest by using AES GCM 256 and envelope encryption. Refer to [Securing your data with encryption](https://cloud.ibm.com/docs/schematics?topic=schematics-secure-data).





 How are cloud resources isolated from other tenants? 

When you use Schematics to provision IBM Cloud resources, these resources are created in your personal IBM Cloud account. You are responsible to manage these resources and to keep them up-to-date to avoid security vulnerabilities or downtime for your workloads. IBM Cloud resources are provisioned, updated, and deleted as defined in the Terraform template and requested by the user.

Because all resources are created in your personal account, resources are not shared with or reused by other IBM Cloud tenants.
IBM Cloud Schematics docs 

Explore the capabilities of IBM Cloud Schematics. You can get started with deploying platform services by using Schematics Workspaces, and automating cloud operations with Schematics Actions. Learn more about how Schematics works and the benefits of using the service.

 Developer tools 

[API & SDK reference](https://cloud.ibm.com/apidocs/schematics)[CLI reference](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-reference)[Terraform reference](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/schematics_action)

 Recommended content 

[Automate cloud operations with actions Learn how to automatically start and stop a Virtual Servers for VPC instance with an IBM-provided Ansible playbook.](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started-ansible)[Extend provisioning through Agents Learn how to provision, configure, and operate your private or on-premises cloud cluster resources without any time, network, or software restrictions.](https://cloud.ibm.com/docs/schematics?topic=schematics-agentb1-about-intro)[Deploy complex application environments using Blueprints Learn how to deploy large-scale and complex application environments from reusable building blocks and used across multiple environments.](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-intro)[Deploy cloud services with workspaces Use an IBM-provided Terraform template to create an Object Storage service instance to store your data in IBM Cloud.](https://cloud.ibm.com/docs/schematics?topic=schematics-get-started-terraform)[Explore the IBM Cloud software catalog Try out one of the IBM-provided software templates to quickly spin up a classic virtual server instance (VSI), and automatically configure the instance to connect to an IBM Cloud Database.]
Schematics Blueprints is a [beta feature](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitations) that are available for evaluation and testing purposes. It is not intended for production usage. Refer to the list of [limitations](https://cloud.ibm.com/docs/schematics?topic=schematics-bp-beta-limitationssc-bp-beta-limitation) for the beta release.



 Understanding blueprints and environments 

Schematics Blueprints brings [infrastructure as code (IaC) practices](https://cloud.ibm.com/docs/schematics?topic=schematics-infrastructure-as-code) to the creation and lifecycle management of large-scale cloud environments. It uses the analogy of a blueprint used in construction, to define and deploy cloud environments from reusable modules of Terraform code. Blueprint operations take cloud environments from their initial creation, through maintenance and ops to final decommissioning and clean up of all allocated resources.

Review the section [About Schematics Blueprints](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-intro) for more background. A key feature of Blueprints is support to take cloud environments through their life, from creation to final removal.

Blueprints enables users to define and deploy cloud environments using modules of reusable and well-defined [Terraform](https://www.terraform.io) automation code. This builds on the IaC best practice of [modular architectures](https://cloud.ibm.com/docs/schematics?topic=schematics-infrastructure-as-codeiac-bp-modularity), where reusable modules implement the layers and components of an infrastructure architecture from well designed, tested and compliant Terraform code.



 Cloud infrastructure lifecycle 

Schematics Blueprints follows an lifecycle operations model. Cloud environments, hosted applications or services all follow a lifecycle from creation to end-of-life. The life of a blueprint environment starts with the initial definition of an infrastructure architecture and configuration.
* What tools and utilities used in the runtime?

Schematics runtime is built by using Universal Base Image (UBI-8) and the runtime utilities/softwares that come with the UBI-8 are available for Terraform provisions and Ansible actions. For more information, see the list of [tools and utilities](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-utilities) used in Schematics runtime.
* How can I fix Git token issues when creating workspaces using the CLI

Using schematics workspace new --file schematic-file.json -g xxxx command throws an Access token creation failed status, as the token is not specified in the command.

You need to check your [authentication](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-apics_api) before performing the operation through command-line. Then, create a workspace by using schematics workspace new --file schematic-file.json --github-token xxxx command. For more information, see [ibmcloud schematics workspace new](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-new) command.
* How do I fix authorization issues when creating or updating a workspace?

You see authorization issues when the roles and permission access is insufficient while updating workspace. For more information, see [Managing user access](https://cloud.ibm.com/docs/schematics?topic=schematics-access).
* How can I use Schematics services with a test ID?

The test IDs are considered as a valid IBM ID to set the global catalog or resource controller-related API calls. If you are unable to access, do [Contact support service](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-help).
* How to limit Git repo folder cloning