vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Discovery 

The installable IBM Watson® Discovery service is a cognitive search and content analytics engine that you can add to applications to identify patterns, trends, and actionable insights to drive better decision-making. Securely unify structured and unstructured data with pre-enriched content, and use a simplified query language to eliminate the need for manual filtering of results. For more information about this service, see [Discovery](https://cloud.ibm.com/docs/discovery?topic=discovery-about).

The Watson packages are deprecated. Please use the [Watson SDKs](https://cloud.ibm.com/docs/watson?topic=watson-using-sdks) to perform Watson related functionality. For more information about which Watson SDK is included in the available runtimes, see the [Functions runtime](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimes) documentation.

The Discovery package contains the following entities. You can find more details in the Discovery API reference by clicking the entity name.



Table 1. Discovery package entities

 Entity Type Parameters Description 

 [discovery-v1](https://cloud.ibm.com/apidocs/discovery) Package username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url Work with the Discovery service. 
 [create-environment](https://cloud.ibm.com/apidocs/discoverycreate-an-environment) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, name, description, size Create an environment. 
 [delete-environment](https://cloud.ibm.com/apidocs/discoverydelete-environment) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, environment_id Delete an environment.
Using a Cloud Pak for Data custom crawler plug-in from the Discovery user interface 

After you build and deploy a crawler plug-in, you can configure your Discovery collection to use your plug-in to process documents.

IBM Cloud Pak for Data

IBM Cloud Pak for Data only

This information applies only to installed deployments.



*  You can create and manage a collection as described in [Creating and managing collections](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collections).
*  You can select a successfully deployed crawler plug-in when you create and manage a collection.

For more information, see [Crawler plug-in settings](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesplugin-settings).
*  You can also deploy a crawler plug-in package to a testing environment.
[2000003 - FAQ: SAP HANA](https://launchpad.support.sap.com//notes/2000003) Extensive overview of SAP HANA 
 [1999880 - FAQ: SAP HANA System Replication](https://launchpad.support.sap.com//notes/1999880) HSR central note 
 [2000002 - FAQ: SAP HANA SQL Optimization](https://launchpad.support.sap.com//notes/2000002) Useful tips to improve SQL processing times 
 [SAP HANA Platform Landing page](https://help.sap.com/viewer/product/SAP_HANA_PLATFORM/2.0.05/en-US?task=discover_task) Useful for installation guides and upgrade guides 
 [SAP Guide Finder](https://help.sap.com/viewer/nwguidefinder/576f5c1808de4d1abecbd6e503c9ba42.html) Useful to locate user guides and information on updates 
 [2380291 - SAP HANA 2.0 Cockpit Central Release Note](https://launchpad.support.sap.com//notes/2380291) SAP HANA Cockpit central note
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/c2338e66-dcb5-4e9b-b572-108d47ca479a",
"id": "c2338e66-dcb5-4e9b-b572-108d47ca479a",
"name": "my-subnet",
"resource_type": "subnet"
},
"transit_encryption": "provider_managed",
"virtual_network_interface": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/virtual_network_interfaces/4551a68d-b45d-4443-b6b3-aba7a4a18c98",
"id": "4551a68d-b45d-4443-b6b3-aba7a4a18c98",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/5821d0c4-a089-4957-b5fa-03b7ac636c15",
"id": "5821d0c4-a089-4957-b5fa-03b7ac636c15",
"name": "my-vpc",
"resource_type": "vpc"
}
}
Show more





 View a source file share for a replica file share with the API 

Make a GET /shares/{replica_id}/source request and specify the replica share ID to retrieve the source file share details.
PIPELINE_CONFIG_REPO_PATH The directory where the pipeline config-repo is cloned. 
 PIPELINE_RUN_NAME The Tekton pipeline run name. 
 PIPELINE_RUN_ID The Tekton pipeline run ID. 
 PIPELINE_RUN_URL The Tekton pipeline run URL. 
 PIPELINE_ID The Tekton pipeline ID. 
 STAGE The user script stage. 
 TOOLCHAIN_DATA_PATH The toolchain data path /toolchain/toolchain.json file. 
 TRIGGER_TYPE The pipeline trigger type. 
 TRIGGER_NAME The pipeline trigger name. 
 TRIGGER_PAYLOAD (DEPRECATED) The payload that is received by way of the pipeline trigger event, if there was one. For more information about working with payloads, see [Accessing arguments from webhook payloads](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-webhook-payloads). 
 TRIGGERED_BY Information about who triggered the pipeline. This value can be an email address or a time-triggered pipeline run. 
 WORKSPACE The path to the shared workspace. 
 PIPELINE_STATUS Status of the pipeline run, can be "Succeeded", "Failed", or blank. PIPELINE_STATUS is available in finish stages only 



You can access these environment variables in any script, for example, ${PIPELINE_ID}.







 Accessing toolchain data from custom scripts 

You can read toolchain data from the toolchain.json file that is provided by the pipeline at the path that is stored in the TOOLCHAIN_DATA_PATH environment variable. You can also use the toolchain integration and jsonpath, and access them in /config in the same way as any other variable. Or, you can use get_env, which has the same effect.



 Example usage 

TOOLCHAIN_CONFIG_JSON="$(get_env TOOLCHAIN_CONFIG_JSON)"
toolchain_id=$(jq -r '.toolchain_guid' "$TOOLCHAIN_CONFIG_JSON")
GET /_scheduler/docs/_replicator/$doc_id <br>[Cloudant](https://cloud.ibm.com/apidocs/cloudantgetschedulerdocument), [CouchDB](https://docs.couchdb.org/en/latest/replication/replicator.html) Retrieve a replication scheduler document. 
 HEAD /_scheduler/docs/_replicator/$doc_id <br>[CouchDB](https://docs.couchdb.org/en/latest/replication/replicator.html) Retrieve the HTTP headers for a particular replication scheduler document. 
 GET /_scheduler/jobs <br>[Cloudant](https://cloud.ibm.com/apidocs/cloudantgetschedulerjobs), [CouchDB](https://docs.couchdb.org/en/latest/api/server/common.htmlscheduler-jobs) Retrieve replication scheduler jobs. 
 HEAD /_scheduler/jobs <br>[CouchDB](https://docs.couchdb.org/en/latest/api/server/common.htmlscheduler-jobs) Retrieve the HTTP headers for replication scheduler jobs. 
 GET /_scheduler/jobs/{job_id} <br>[Cloudant](https://cloud.ibm.com/apidocs/cloudantgetschedulerjob) Retrieve the state of a single replication task based on its replication ID. 
 HEAD /_scheduler/jobs/{job_id} <br>[Cloudant](https://cloud.ibm.com/apidocs/cloudantheadschedulerjob) Retrieve the HTTP headers of a single replication task based on its replication ID. 
 POST /_search_analyze <br>[Cloudant](https://cloud.ibm.com/apidocs/cloudantpostsearchanalyze), [CouchDB](https://docs.couchdb.org/en/latest/api/server/common.htmlsearch-analyze) Retrieve the results of analyzer tokenization of the provided sample text.
api_token: "crn:v1:bluemix:public:secrets-manager:us-south:a/9bb43e401a7a87d15145da761da98571:604de62c-c04f-3f5e-b7e8-4acafe0ecde7:secret:5ec17023-b631-fbcb-ef9c-4f2eb01f1dda",
channel_name: "my_slack_channel_name",
team_url: "my_slack_team_name"
};

const toolPrototypeModel = {
toolchainId: "01234567-89ab-cdef-0123-456789abcdef",
toolTypeId: "slack",
parameters: slackParameters
};

const slackTool = await toolchainService.createTool(toolPrototypeModel);
})();

from ibm_continuous_delivery.cd_toolchain_v2 import CdToolchainV2
...
toolchain_service = CdToolchainV2.new_instance()
slack_parameters = {
"api_token": "crn:v1:bluemix:public:secrets-manager:us-south:a/9bb43e401a7a87d15145da761da98571:604de62c-c04f-3f5e-b7e8-4acafe0ecde7:secret:5ec17023-b631-fbcb-ef9c-4f2eb01f1dda",
"channel_name": "my_slack_channel_name",
"team_url": "my_slack_team_name"
}
slack_tool = toolchain_service.create_tool(
![How to find peer fabric version](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/peerversion.png)

Figure 1.How to find peer fabric version



 Hyperledger Fabric v2.x peer image 

![version 2.x](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/2-x_Pill.png) While the terms "smart contract" and "chaincode" are often used interchangeably, "smart contracts" refers to the business logic that governs transactions and access to its data, while "chaincode" refers to the larger infrastructure of packages and other code that encompasses a smart contract.

If your peer is based on the Hyperledger Fabric v2.x image, you can run the following set of kubectl commands to view the smart contract logs.

Find your cluster namespace

If you don't already know it, you need to find your Kubernetes cluster namespace. From the console, open any CA node and click the Info and Usage icon. View the value of the API URL. For example: https://nf85a2a-soorg10524.ibpv2-cluster.us-south.containers.appdomain.cloud:7054. The namespace is the first part of the URL beginning with the letter n and followed by a random string of six alphanumeric characters. So in the example above the value of the namespace is nf85a2a.

Find the smart contract pod

Next, get a list of all of the smart contract pods running in your cluster:

kubectl get po -n <NAMESPACE> | grep chaincode-execution | cut -d" " -f1 | xargs -I {} kubectl get po {} -n <NAMESPACE> --show-labels
"api_token": "crn:v1:bluemix:public:secrets-manager:us-south:a/9bb43e401a7a87d15145da761da98571:604de62c-c04f-3f5e-b7e8-4acafe0ecde7:secret:5ec17023-b631-fbcb-ef9c-4f2eb01f1dda",
"channel_name": "my_slack_channel_name",
"team_url": "my_slack_team_name"
}
slack_tool = toolchain_service.create_tool(
toolchain_id = "01234567-89ab-cdef-0123-456789abcdef",
tool_type_id = "slack",
parameters = slack_parameters
)

import (
"github.com/IBM/continuous-delivery-go-sdk/cdtoolchainv2"
)
...
toolchainClientOptions := &cdtoolchainv2.CdToolchainV2Options{}
toolchainClient, err := cdtoolchainv2.NewCdToolchainV2UsingExternalConfig(toolchainClientOptions)
slackParameters := map[string]interface{}{
"api_token": "crn:v1:bluemix:public:secrets-manager:us-south:a/9bb43e401a7a87d15145da761da98571:604de62c-c04f-3f5e-b7e8-4acafe0ecde7:secret:5ec17023-b631-fbcb-ef9c-4f2eb01f1dda",
"channel_name": "my_slack_channel_name",
[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/components/watson-discovery/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture/architectures/cognitiveDiscoveryDomain)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/artificial-intelligence)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/watsonai/communities/community-home?CommunityKey=80650291-2ff4-4a43-9ff8-5188fdb9552f)
AppID Management 



 Resources Data sources 

 <br><br> * [ibm_appid_action_url](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/appid_action_url)<br> * [ibm_appid_apm](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/appid_apm)<br> * [ibm_appid_application](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/appid_application)<br> * [ibm_appid_application_roles](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/appid_application_roles)<br> * [ibm_appid_application_scopes](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/appid_application_scopes)<br> * [ibm_appid_audit_status](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/appid_audit_status)<br> * [
* [SAP HANA System Replication Scale-Up - Performance Optimized Scenario](https://documentation.suse.com/sbp/all/html/SLES4SAP-hana-sr-guide-PerfOpt-12/index.html)
* [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/)



Red Hat Enterprise Linux for SAP:



* [Supported HA Scenarios for SAP HANA, SAP S/4HANA, and SAP NetWeaver](https://access.redhat.com/articles/4079981)
* [Automated SAP HANA System Replication in Scale-Up in pacemaker cluster](https://access.redhat.com/articles/3004101)
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_keys/3dab42dc-6941-4841-8d27-4dabcc5aa09e"
}







 hpcs uko associated-resources-for-managed-key 

Obtain a list of resources associated with a managed key in IBM Cloud. These cloud resources are protected by the key that you specify.

If the --all-pages option is not set, the command only retrieves a single page of the collection.

ibmcloud hpcs uko associated-resources-for-managed-key --id ID --uko-vault UKO-VAULT [--limit LIMIT] [--offset OFFSET] [--sort SORT]



* Command options

--id (string)
: Required. The UUID of the key. You can use the ibmcloud hpcs uko managed-keys command to retrieve the key UUID.

--uko-vault (string)
: Required. The UUID of the vault where the update is to take place. You can use the ibmcloud hpcs uko vaults command to retrieve the vault UUID.

--limit (int64)
: Optional. The number of resources to retrieve. The value must be between 1 and 1000.

--offset (int64)
: Optional. The number of resources to skip. The minimum value is 0.

--sort ([]string)
: Optional. The sorting order. The default value is ["name"]. The list items must match the regular expression /^-?[a-z0-9_.\[\],-]+$/.

--all-pages (bool)
: Optional. Invoke multiple requests to display all pages of the collection for the associated resources.
* Example

ibmcloud hpcs uko associated-resources-for-managed-key
"ibm_api_endpoint": "https://us-south.kms.cloud.ibm.com",
"ibm_iam_endpoint": "https://iam.bluemix.net/identity/token",
"ibm_api_key": "",
"ibm_instance_id": "d139ea58-a073-441b-ba4e-dcc8bae58be4",
"ibm_variant": "hpcs",
"ibm_key_ring": "IBM-Cloud-KMS-Internal"
}







 hpcs uko associated-resources-for-target-keystore 

Obtain a list of resources associated with all keys that are activated in this keystore.

If the --all-pages option is not set, the command only retrieves a single page of the collection.

ibmcloud hpcs uko associated-resources-for-target-keystore --id ID --uko-vault UKO-VAULT [--limit LIMIT] [--offset OFFSET] [--sort SORT]



* Command options

--id (string)
: Required. The UUID of the keystore. You can use the ibmcloud hpcs uko keystores command to retrieve the UUID.

--uko-vault (string)
: Required. The UUID of the vault where the update is to take place. You can use the ibmcloud hpcs uko vaults command to retrieve the vault UUID.

--limit (int64)
: Optional. The number of resources to retrieve. The value must be between 1 and 1000.

--offset (int64)
: Optional. The number of resources to skip. The minimum value is 0.

--sort ([]string)
: Optional. The sorting order. The default value is ["name"]. The list items must match the regular expression /^-?[a-z0-9_.\[\],-]+$/.

--all-pages (bool)
"version": "1.0.0",
"date": "2020-05-06T12:00:00Z", // date of task run
"origin": {
"url":"https://us-south.git.cloud.ibm.com/open-toolchain/compliance-pipelines/-/blob/master/definitions/mytask.yaml", // where the task is taken from
"version": "423792" // commit id representing the task version used to produce the evidence
}
"toolchain_crn": "crn:v1:bluemix:public:toolchain:us-south:a/190e0b4ce4cd013159917665213ddc51:7467a214-f404-4e23-acab-2e57e935d138::" // CRN of the toolchain
"pipeline_id": "b1cfb6a4-813d-4fec-bbf7-ce662e8ce4e0", // the id of the pipeline that generated this piece of evidence
"pipeline_run_id": 12345, // this is the id of the pipeline run that generated this piece of evidence
"result": "passed" | "failed"], // status of the check
"status": "enabled"|"disabled"], // status of the configuration
"issues": // link(s) to the issue(s) created to fix the github configuration (should be populated if result is failed)
"https://acme.org/foo/123",
"https://acme.org/foo/124",
"https://acme.org/foo/125",
],
"log": {
"url": "https://acme.org/log.txt", // the link to where the actual log of the test is
"hash": "abc123", // the hash of the log file
},
Continuous Delivery 



 Resources Data sources 

 <br><br> * [ibm_cd_tekton_pipeline](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline)<br> * [ibm_cd_tekton_pipeline_definition](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline_definition)<br> * [ibm_cd_tekton_pipeline](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline_property)<br> * [ibm_cd_tekton_pipeline_property](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-resources-datasource-list)<br> * [ibm_cd_tekton_pipeline_trigger](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline_trigger)<br> * [ibm_cd_tekton_pipeline_property](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline_trigger_property)<br> * [ibm_cd_toolchain](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_toolchain)<br> * [
[Administrator step] Type the client ID from https://app.box.com/developers/console into the API key field and then click the Authorize button.
3. Return to the Box developer console https://app.box.com/developers/console and scroll to the Add and Manage Public Keys section. Click the Generate the public/private keypair and download your keypair file. Open the file.
4. From the keypair file, cut and paste the following fields into the Discovery tooling.



* client_id
* enterprise_id
* client_secret
* public_key_id
* private_key
* passphrase





Other items to consider when you crawl Box:



* Box notes are stored in JSON format, so Discovery ingests any Box notes in the specified folders.
* When you use the API, you must have a list of Folders IDs and the associated Owner ID for each folder that you want to crawl. Use the Discovery tooling to browse and select which content to crawl.









 Salesforce 

When connecting to a Salesforce source, ensure that the instance you plan to connect to is an Enterprise plan or higher.

The following credentials are required to connect to a Salesforce source. If you do not know these credentials, consult your Salesforce administrator:



* url - The url of the source that these credentials connect to.
* username - The username of the source that these credentials connect to.
* password - The password consists of the Salesforce password and a valid Salesforce security token concatenated. This value is never returned and is only used when creating or modifying credentials.



When identifying the credentials, it might be useful to consult the [Salesforce developer documentation](https://developer.salesforce.com/docs/).

Other items to note when you crawl Salesforce:



* Knowledge Articles are only crawled if their version is published and their languages is en-us.
* When you use the API, you must have a list of Salesforce objects that you want to crawl. Use the Discovery tooling to browse and select which content to crawl.







 SharePoint Online
: Change log documentation is available for version [4.7.30_1532_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474730_1532),[4.6.44_1556_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464644_1556), [4.5.41_1552_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4541_1552), and [3.11.521_1604_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311521_1604).

Worker node fix pack update
: Change log documentation is available for version [4.5.41_1553_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-changelog_archive4541_1553),[4.6.45_1557_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464645_1557), [4.7.31_1533_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474731_1533), and [3.11.521_1605_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311521_1605).





 23 September 2021 

Review the release notes for 23 September 2021.

Istio add-on change log
GET /_api/v2/usage/data_volume and /_api/v2/usage/$YEAR/$MONTH cloudantnosqldb.sapi.usage-data-volume 
 GET/HEAD / cloudantnosqldb.account-meta-info.read 
 GET/HEAD /_active_tasks cloudantnosqldb.account-active-tasks.read 
 GET/HEAD /_replicator cloudantnosqldb.replicator-database-info.read 
 GET/HEAD /_replicator/$DOCUMENT cloudantnosqldb.replication.read 
 GET/HEAD /_scheduler/jobs cloudantnosqldb.replication-scheduler.read 
 GET/HEAD /_scheduler/docs cloudantnosqldb.replication-scheduler.read 
 POST /_replicate cloudantnosqldb.replication.write 
 PUT/DELETE /_replicator cloudantnosqldb.replicator-database.create 
 PUT/DELETE /_replicator/$DOCUMENT cloudantnosqldb.replication.write 
 GET/HEAD /_up cloudantnosqldb.account-up.read 
 PUT /$DATABASE/ cloudantnosqldb.database.create 
 DELETE /$DATABASE cloudantnosqldb.database.delete 
 POST /$DATABASE/_design_docs/queries cloudantnosqldb.any-document.read 
 GET/HEAD /$DATABASE/_design/$DOCUMENT_ID/_geo_info cloudantnosqldb.any-document.read 
 GET/HEAD /$DATABASE/_design/$DOCUMENT_ID/_info/$FURTHER_PATH_PARTS cloudantnosqldb.any-document.read 
 GET /$DATABASE/_design/$DOCUMENT_ID/_search_disk_size/$FURTHER_PATH_PARTS cloudantnosqldb.any-document.read 
 GET /$DATABASE/_design/$DOCUMENT_ID/_search_info/$FURTHER_PATH_PARTS cloudantnosqldb.any-document.read 
 GET/HEAD /$DATABASE/_index/$FURTHER_PATH_PARTS cloudantnosqldb.any-document.read
[112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/home)

 Latest updates 

[View more](https://cloud.ibm.com/docs/subnets?topic=subnets-release-notes-subnets)27 May 2021 | Remove obsolete links

Removed obsolete links from the getting started and ordering topics.