vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can define environment variables for IBM Cloud catalog offerings that are provisioned by using a bash script files. 
 variable_name Optional Enter the name for the input variable that you declared in your Terraform configuration files. 
 variable_type Optional Terraform v0.12 supports string, list, map, bool, number and complex data types such as list(type), map(type), object({attribute name=type,..}), set(type), tuple([type]). 
 variable_value Optional Enter the value as a string for the primitive types such as bool, number, string, and HCL format for the complex variables, as you provide in a .tfvars file. You need to enter escaped string of HCL format for the value, as shown in the example. For more information about how to declare variables in a Terraform configuration file and provide value to schematics, see [Using input variables to customize resources](https://cloud.ibm.com/docs/schematics?topic=schematics-create-tf-configdeclare-variable). [For example](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencesyntax_of_variablevalue) 
 secure Optional Set the secure parameter to true. By default, this parameter is set to false. 
 val1 Optional In the payload you can provide an environment variable that can execute in your workspace during plan, apply or destroy stage. Also values are encrypted and stored in COS. 



IBM Cloud Schematics supports setting up environment variable such as TF_PARALLELISM, TF_LOG. For more information about the list of environment variable and its usage, see [List of environment variables](https://cloud.ibm.com/docs/schematics?topic=schematics-set-parallelismlist-special-env-vars).

Example

ibmcloud schematics workspace new --file example.json







 ibmcloud schematics refresh 

Perform an IBM Cloud refresh action against your workspace.
IBM Cloud CLI (ibmcloud) environment variables 

Use the IBM Cloud® CLI (ibmcloud) environment variables to customize your IBM Cloud CLI environment to suit your needs. For example, you can simplify API key-based login to have multiple different CLI sessions in parallel.



 Get help on the IBM Cloud CLI (ibmcloud) environment variables 

ibmcloud --help

In your shell, set the following environment variables by using a VARIABLE_NAME=VALUE pair directly in front of the shell command, or by using export VARIABLE_NAME=VALUE as a separate command before you run the shell command.





 IBMCLOUD_COLOR=false 

Control colorized output by setting IBMCLOUD_COLOR to true or false.





 IBMCLOUD_VERSION_CHECK=false 

Control the regular versioning check for updating the CLI tool by setting IBMCLOUD_VERSION_CHECK to true or false.





 IBMCLOUD_HTTP_TIMEOUT=5 

Control the time limit in seconds for HTTP requests.





 IBMCLOUD_API_KEY=api_key_value 

Use the ibmcloud login command to authenticate by using an API key. The key can be specified directly as value or by referencing the name of the file that contains the key by using @filename.





 IBMCLOUD_CR_TOKEN=cr_token_value 

The compute resource token used for login, which can either be a token string or a path to a @file.





 IBMCLOUD_CR_PROFILE=profile_value 

The name, ID, or CRN of the linked trusted IAM profile to be used when obtaining the IAM access token. If authenticating as a VPC VSI compute resource, specifying only a trusted profile CRN or ID is supported.





 IBMCLOUD_CR_VPC_URL=url_value 

The custom server URL to use when obtaining an instance identity token and IAM token as a VPC VSI compute resource. This value replaces the default server endpoint of the VPC VSI instance identity token service.





 IBMCLOUD_TRACE=true 

Prints API request diagnostics to stdout. Use this variable to investigate how CLI commands are run.
env_values Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform action. This field must be provided as a list of key-value pairs. Each entry will be a map with one entry where key = variable name and value = value. You can define environment variables for IBM Cloud catalog offerings that are provisioned by using a bash script files. 
 variable_name Optional Enter the name for the input variable that you declared in your Terraform configuration files. 
 variable_type Optional Terraform v0.12 supports string, list, map, bool, number and complex data types such as list(type), map(type), object({attribute name=type,..}), set(type), tuple([type]). 
 variable_value Optional Enter the value as a string for the primitive types such as bool, number, string, and HCL format for the complex variables, as you provide in a .tfvars file. You need to enter escaped string of HCL format for the value, as shown in the example. For more information about how to declare variables in a Terraform configuration file and provide value to schematics, see [Using input variables to customize resources](https://cloud.ibm.com/docs/schematics?topic=schematics-create-tf-configdeclare-variable). [For example](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencesyntax_of_variablevalue) 
 secure Optional Set the secure parameter to true. By default, this parameter is set to false. 
 val1 Optional In the payload you can provide an environment variable that can execute in your workspace during plan, apply or destroy stage. Also values are encrypted and stored in COS. 



IBM Cloud Schematics supports setting up environment variable such as TF_PARALLELISM, TF_LOG.
For more information and more environment variable options, see the [CloudEvent attributes](https://github.com/cloudevents/spec/blob/v1.0.1/spec.mdcontext-attributes).

The following table describes the environment variables that are specific to IBM Cloud Object Storage events.



Table 3. Environment variables for events

 Variable Description 

 CE_DATA The data (body) for the event. See [CE_DATA for Object Storage events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producersubcos-envvar-cedata). 
 CE_ID A unique identifier for the event, unless an event is replayed, in which case, it is assigned the same ID. 
 CE_SOURCE A URI-reference that indicates where this event originated from within the event producer. For Object Storage events, this value is https://cloud.ibm.com/catalog/services/cloud-object-storage/[BUCKET_NAME] where [BUCKET_NAME] is the name of the bucket that contains the object. 
 CE_SPECVERSION The version of the CloudEvents spec. This value is always 1.0. 
 CE_TIME The time that the event was generated. 
 CE_TYPE The type of the event. For Object Storage events, this is com.ibm.cloud.cos.document.[ACTION] where [ACTION] is either write or delete. 





 CE_DATA environment variable 

Notice that the following example for CE_DATA is formatted for readability.

{
"bucket":"mybucket",
"endpoint":"",
"key":"Notes.rtf",
"notification": {
"bucket_name":"mybucket",
"content_type":"text/rtf",
"event_type":"Object:Delete",
"format":"2.0",
"object_length":"4642",
"object_name":"Notes.rtf",
To monitor your infrastructure, network, and applications with the IBM Cloud® Monitoring service, you can deploy Monitoring agents on supported hosts. The host determines the agent type that you can deploy. The agent type determines the metrics that are collected automatically for that host.

To start collecting default metrics, you must configure a Monitoring agent per environment that you want to monitor.

You can monitor hosts in IBM Cloud, on-prem, and in other clouds.



Table 1. Get started working with IBM Cloud Monitoring

 Source Info 

 IBM Cloud services [Enabling platform metrics](https://cloud.ibm.com/docs/docs/monitoring?topic=monitoring-platform_metrics_enabling) <br>[Working with platform metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_working) <br>[Services generating metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-cloud_services) 
 Kubernetes clusters [Monitoring a Kubernetes cluster](https://cloud.ibm.com/docs/monitoring?topic=monitoring-kubernetes_cluster) 
 Red Hat OpenShift clusters [Monitoring a Red Hat OpenShift cluster](https://cloud.ibm.com/docs/monitoring?topic=monitoring-openshift_cluster) 
 VPC/VSI [Monitoring a Linux VPC server instance](https://cloud.ibm.com/docs/monitoring?topic=monitoring-ubuntuubuntu) 
 Bare metal [Monitoring a Linux bare metal server](https://cloud.ibm.com/docs/monitoring?topic=monitoring-baremetal_linux) 
 Windows environments [Monitoring a Windows environment](https://cloud.ibm.com/docs/monitoring?topic=monitoring-windows) 
 Linux environments [Working with the Linux agent](https://cloud.ibm.com/docs/monitoring?topic=monitoring-agent_linux) <br>[Deploying the agent on a Linux host with no public access](https://cloud.ibm.com/docs/monitoring?topic=monitoring-agent_linux_1)
VMware, available in two options:



* Intel Bare Metal and VMware vSphere (ESXi OS), requires manual VMware setup and configuration
* IBM Cloud for VMware Solutions Dedicated





Bare Metal and both VMware options are SAP-certified.

Classic Virtual Servers are not SAP-certified. For this type of IaaS, the IBM Cloud VPC Infrastructure environment provides Intel Virtual Servers which are SAP-certified.

For more information, see [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings).
For example, an IBM Cloud Object Storage service credential variable that is named apikey is available in an environment variable that is called CLOUD_OBJECT_STORAGE_APIKEY. The following example shows the environment variables that are created for an IBM Cloud Object Storage service instance binding.

CLOUD_OBJECT_STORAGE_APIKEY=xxxxxx
CLOUD_OBJECT_STORAGE_ENDPOINTS=https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints
CLOUD_OBJECT_STORAGE_IAM_APIKEY_DESCRIPTION=Auto-generated for key abcdabcd-abcd-abcd-abcd-abcdabcdabcd
CLOUD_OBJECT_STORAGE_IAM_APIKEY_NAME=my-object-storage-codeengine-credential
CLOUD_OBJECT_STORAGE_IAM_ROLE_CRN=crn:v1:bluemix:public:iam::::serviceRole:Manager
CLOUD_OBJECT_STORAGE_IAM_SERVICEID_CRN=crn:v1:bluemix:public:iam-identity::a/1176a104ad4441e6b0aa92ed0b60b15c::serviceid:ServiceId-abcdabcd-abcd-abcd-8b41-531fc64e640e
CLOUD_OBJECT_STORAGE_RESOURCE_INSTANCE_ID=crn:v1:bluemix:public:cloud-object-storage:global:a/1176a104ad4441e6b0aa92ed0b60b15c:11179ac4-abcd-4887-abcd-d330a430abcd::
CLOUD_OBJECT_STORAGE_SERVICENAME=my-object-storage

By default, if more than one instance of the same type is bound to a single application, Code Engine appends an index to the service name, such as CLOUD_OBJECT_STORAGE_2_APIKEY.

Each service binding can be configured to use a custom environment variable prefix. If you are using the console, you can optionally provide a prefix when you create the service binding.
Extract the file when the download is complete.



You can then import the nodes of your network into the extension.



 Importing from IBM Cloud 



1. Hover your mouse over the Fabric Environments pane and click +, Add Environment.
2. Select Add an IBM Blockchain Platform environment.
3. Select Yes when asked whether to connect to an IBM Blockchain Platform service instance on IBM Cloud.
4. Select Log in with username and password or another method.
5. Enter your IBM Cloud username (email address).
6. Enter your IBM Cloud password.
7. The extension will now try to discover any IBM Blockchain Platform service instances - if you have multiple, select the instance to import.
8. Enter a name for your environment.
9. Select the CAs and peers that belong to your organization, along with the ordering nodes of your channels, click OK when done.







 Importing from a Kubernetes cluster not in IBM Cloud 



1. Hover your mouse over the Fabric Environments pane and click +, Add Environment.
2. Select Add an IBM Blockchain Platform environment.
3. Select No when asked whether to connect to an IBM Blockchain Platform service instance on IBM Cloud.
4. Enter the URL of the IBM Blockchain Platform Console software instance.
5. Enter the User ID for the console instance.
6. Enter the Password for the console instance.
7. Select Proceed without certificate verification, or Cancel if you're planning to add the CA certificates to the operating systems trusted CA certificate store.
8. Enter a name for your environment.
9. Select the CAs and peers that belong to your organization, along with the ordering nodes of your channels, click OK when done.
For more information, see [Getting started with IBM Cloud Gateway Appliance](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-getting-started). - The IBM Cloud gateway appliance allows you to selectively route private and, optionally, public network traffic through a full-featured, enterprise-level firewall that is powered by the software features of; VyOS, JunOS, or any other operating system (Bring Your Own Appliance) you choose. - All appliance features are customer-managed. - By using the IBM Cloud UI, CLI, or API, you can select your VLANs, and hence, the associated subnets that you want to associate with your gateway appliance. Associating a VLAN with a gateway appliance reroutes (or trunks) that VLAN and all of its subnets to your appliance, giving you control over filtering, forwarding, and protection. - A gateway appliance is attached to two nonremovable transit VLANs, one each for your public and private networks.

Complete the following steps to implement this scenario:



1. [Set up an IBM Cloud Gateway Appliance](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-getting-started).
2. Complete all steps that are mentioned in [Connect-to-classic infrastructure by using IBM Direct Link](https://cloud.ibm.com/docs/gateway-appliance?topic=power-iaas-network-architecture-diagramsnetwork-reference-architecture-privatessl). It includes configuring Power Systems Virtual Server private subnets and provisioning a Direct Link (2.0) Connect or an IBM Cloud connection instance with the VRF option.
3. The IBM Cloud classic infrastructure environment VRF contains the following routes:



* Subnets that are assigned to you by IBM Cloud for use in your classic environment.
* Your Power Systems Virtual Server subnets advertised by the Power Systems Virtual Server router.



However, it does not contain routes to your remote networks.
Accessing the environment 

After successful deployment, IBM Cloud Schematics provides an output log that lists all IP addresses of created VPC instances. These IP addresses include: - An access host IP address that is the entry point to the whole landscape. - NFS, DNS, NTP server IP addresses.

The Power Virtual Server with VPC landing zone deployable architecture creates secure and isolated environment. Network communication with the public internet and other landscapes sitting outside of the configured environment is prohibited. Opening the management network channel, for example, for the access with administrator laptop, is the step that must be done manually. In general, there a couple of options for such configuration:



1. Open the VPN connection to the management VPC where access to the host is located.
2. Add an additional IP address to the network access control list of the management VPC where access host is located. You can configure the IBM Cloud® Virtual Private Cloud (VPC) by using the IBM Cloud console.
3. Open [IBM Cloud console ![External link icon](https://cloud.ibm.com/docs-content/v1/content/ff1a3be52df84c2eedbc21905c0bcfa13a27e767/icons/launch-glyph.svg)](https://cloud.ibm.com/login).
4. Click Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Network > VPCs
5. In the navigation pane, click Network > Subnets.
6. Click the subnet that you created.
7. In the Subnet details area, click the name of the ACL.
8. Select the region where you completed the deployment and the access control list named '[prefix]-management-acl', where [prefix] corresponds to the one specified by deployment.
9. Insert following rules:
The ISO certification covers a family of 4 standards as follows:



* ISO/IEC 27001:2013
* ISO/IEC 27017:2015
* ISO/IEC 27018:2019
* ISO/IEC 27701:2019



For more information, see [ISO 27017 - IBM Cloud infrastructure certificate](https://www.ibm.com/downloads/cas/GLL9ZBZX) and [Products in scope of the IBM services information security management system (ISMS).](https://www.ibm.com/downloads/cas/OELMNOND).





 PCI-DSS 

To ensure consistent standards for merchants, the Payment Card Industry Security Standards Council established the Payment Card Industry (PCI) data security standards. These standards incorporate best practices to protect cardholder data, and they often require validation from a third-party Qualified Service Assessor (QSA). IBM is a Level 1 Service Provider for PCI DSS.

You are responsible for the storing, processing, and transmission of cardholder data and may create cardholder data environments (CDEs) that can store, transmit, or process cardholder data using IBM Cloud Platform services. You can use the IBM Cloud Attestation of Compliance (AOC) when you seek your own PCI DSS certifications. It is your responsibility to document and operate CDEs and applications built using IBM Cloud Platform services in a PCI DSS-compliant manner.

Contact an [IBM representative](https://www.ibm.com/account/reg/signup?formid=MAIL-wcp) to request a PCI DSS Attestation of Compliance (AOC) and/or a Service Responsibility Matrix (SRM) guide for Power Systems Virtual Server.

You can build PCI DSS compliant environments and applications using IBM Cloud. For more information, see [IBM Cloud PCI DSS Guidance](https://www.ibm.com/downloads/cas/OPLDK4Q2).
It includes configuring Power Systems Virtual Server private subnets and provisioning a Direct Link (2.0) Connect or an IBM Cloud connection instance with the VRF option.
3. The IBM Cloud classic infrastructure environment VRF contains the following routes:



* Subnets that are assigned to you by IBM Cloud for use in your classic environment.
* Your Power Systems Virtual Server subnets advertised by the Power Systems Virtual Server router.



However, it does not contain routes to your remote networks. Static routes or a routing protocol, such as BGP, shares routes between your remote network and the gateway appliance. The routes that are advertised by the gateway appliance include your Power Systems Virtual Server subnets.
4. Configure a GRE tunnel between the gateway appliance and the Power Systems Virtual Server router as this router doesn't have routes for your remote networks that are advertised to it through the IBM Cloud-side router. Within the GRE tunnel, static routes are configured between the Power Systems Virtual Server router and the gateway appliance. For more information, see [Configuring Generic Routing Encapsulation (GRE) tunnel](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-cloud-connectionsconfigure-gre-tunnel).
5. Set up a separate Direct Link (2.0) connection between your remote network (on-premises) and the IBM Cloud classic infrastructure. See [Getting started with IBM Cloud Direct Link (2.0)](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl), however, key elements of IBM Cloud Direct Link (2.0) include the following:



* Requires BGP to establish the routes to a customer's remote network.
* Each IBM Cloud Direct Link service is not redundant, however, diversity can be enabled over multiple Direct Links along with BGP.
* Ensure that IP subnet overlaps do not exist between the infrastructure environments and the remote networks.



6.
variable_value Optional Enter the value as a string for the primitive types such as bool, number, string, and HCL format for the complex variables, as you provide in a .tfvars file. You need to enter escaped string of HCL format for the value, as shown in the example. For more information about how to declare variables in a Terraform configuration file and provide value to schematics, see [Using input variables to customize resources](https://cloud.ibm.com/docs/schematics?topic=schematics-create-tf-configdeclare-variable). [For example](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referencesyntax_of_variablevalue) 
 secure Optional Set the secure parameter to true. By default, this parameter is set to false. 
 val1 Optional In the payload you can provide an environment variable that can execute in your workspace during plan, apply or destroy stage. Also values are encrypted and stored in COS. 



IBM Cloud Schematics supports setting up environment variable such as TF_PARALLELISM, TF_LOG. For more information about the list of environment variable and its usage, see [List of environment variables](https://cloud.ibm.com/docs/schematics?topic=schematics-set-parallelismlist-special-env-vars).

Example

ibmcloud schematics workspace new --file example.json







 ibmcloud schematics refresh 

Perform an IBM Cloud refresh action against your workspace. A refresh action validates the IBM Cloud resources in your account against the state that is stored in the Terraform state file of your workspace. If differences are found, the Terraform state file is updated accordingly.

Syntax

ibmcloud schematics refresh --id WORKSPACE_ID [--output OUTPUT]

Command options



Schematics refresh flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace that you want to refresh and run an action against.
For a complete list of the predefined environment properties, see [Environment properties and resources](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-deliverypipeline_environment).

You can also define your own environment properties. For example, you might define an API_KEY property that passes an API key that is used to access IBM Cloud resources by all scripts in the pipeline.

You can add the following types of properties:



* Text: A property key with a single-line value.
* Text Area: A property key with a multi-line value. A base64 version of each text area property value is also available. You can access this version by using the property key name with a trailing _base641 suffix. You can decode the base64 version of a Text Area property and echo it by typing echo "$(echo $multi_base64 | base64 -d)", where multi is the property key name you defined and multi_base64 is the additional property that is provided. The pipeline base image contains built in support to manage multi-line encoding transparently. However, if you use a custom image you must append the _base64 suffix property to prevent issues where your value is truncated by a line-ending.
* Secure: A property key with a single-line value that is secured with AES-128 encryption. The value is displayed as asterisks.
* Properties: A file in the project's repository. This file can contain multiple properties. Each property must be on its own line. To separate key-value pairs, use the equals sign (=). Enclose all string values in quotation marks. For example, MY_STRING="SOME STRING VALUE".



You can examine the environment properties for a pipeline job by running the env command in the job's script.



 Pipeline properties 

To define pipeline properties, from the overflow menu on the Pipeline page, select Configure Pipeline.

Zoom

!