vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespacescreate_iam_namespace)
5. On your local computer, create a Python virtual environment to install the requirements.

If you are running a Windows system, run the following commands:

pip install virtualenv
mkdir twilio
virtualenv twilio
cd twilio/scripts
pip install twilio
deactivate

If you are running a Unix or MacOS system, run the following commands:

pip install virtualenv
mkdir twilio
cd twilio
virtualenv virtualenv
source virtualenv/bin/activate
pip install twilio
deactivate
6. Create a new file named __main__.py with a new function named twilio.

 Download the helper library from https://www.twilio.com/docs/python/install
import os
from twilio.rest import Client

def twilio(args):
 Find your Account SID and Auth Token at twilio.com/console
 and set the environment variables. See http://twil.io/secure
account_sid = "<YOUR_ACCOUNT_SID>"
auth_token = "<YOUR_AUTH_TOKEN>"
client = Client(account_sid, auth_token)

message = client.messages 
.create(
body="Alert detected in your Sysdig instance" ,
from_='<TWILIO_NUMBER>',
to='<YOUR_DESTINATION_NUMBER>'
)

return {"result": "Message status " + message.status}
Show more

Where:



* YOUR_ACCOUNT_SID is your Twilio SID that can be found at [twilio.com/console](http://www.twilio.com/console).
pod 'ENPushDestination', '> 0.0.1'
end





 Carthage 

To install ENPushDestination using Carthage, add the following to your Cartfile.

github "IBM/event-notifications-destination-ios-sdk" > 0.0.1

Then, run the following command to build the dependencies and frameworks:

carthage update --platform iOS





 Swift Package Manager 

Add the following to your Package.swift file to identify ENPushDestination as a dependency. The package manager clones ENPushDestination when you build your project with swift build.

dependencies: [
.package(url: "https://github.com/IBM/event-notifications-destination-ios-sdk", from: "0.0.1")
]







 Installation - Initialize SDK 

Complete the following steps to enable iOS applications to receive notifications.



1. Add the import statements in your .swift file.

import ENPushDestination
2. Initialize the ENPushDestination SDK

let instanceGUID = "<instance_guid>>";
let destinationID = "<instance_destination_id>";
let apiKey = "<instance_apikey>";

let enPush = ENPush.sharedInstance
enPush.setCloudRegion(region: .usSouth)
enPush.initialize(instanceGUID, destinationID, apiKey)



* region: Region of the Event Notifications instance. For example, Region.usSouth.









 Register for notifications 

Use the ENPush.registerDevice() API to register the device with iOS destination in Event Notifications service.

The following options are supported:



* Register without userId:

/Register iOS devices/
enPush.registerWithDeviceToken(deviceToken: "<apns-device-token>") { response, statusCode, error in
print(response?.id ?? "")
}
* Register with UserId.
config_data = json.load(file)

    api_key = config_data["template_data"]["variablestore"]["value"]

    schematic_obj = HPCCEnvironmentValues(api_key)

    workspace_response = schematic_obj.schematics_service.get_workspace(w_id="<workspace id>").get_result()
    schematic_obj.update_variables(w_id="<workspace id>", 
        t_id=workspace_response["template_data"]["id"], 
        variablestore=config_data["template_data"]["variablestore"]
    )

logging.info("Schematic Variable Update Completed")
Show more





 Example Python request for schematics_env_class.py file 

import json
import logging

from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
from ibm_schematics import SchematicsV1

class HPCCEnvironmentValues:

    def __init__(self, api_key):
        """
        create schematic services
        """
        self.authenticator = IAMAuthenticator(api_key)
        self.schematics_service = SchematicsV1(authenticator=self.authenticator)

        self.schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')
        logging.info("Schematic Services created")

    def update_variables(self, w_id, t_id, variablestore):

        print("Function Schematic Update Variables Started")
        variables_update_result = self.schematics_service.replace_workspace_inputs(w_id=w_id, t_id=t_id, variablestore=variablestore
    ).get_result()

        return variables_update_result   
Show more





 config.json template file
<br><br> * Node.js 10<br> * Node.js 12<br> * Python 3<br><br><br> [Code](https://github.com/ibm-functions/template-get-external-resource) 
 [Hello World](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-templateshello-world-template) Create a basic action that accepts a JSON object as a single parameter. <br><br> * Node.js 10<br> * Node.js 12<br> * Python 3<br> * PHP 7<br><br><br> [Code](https://github.com/ibm-functions/template-hello-world) 
 [IBM® Event Streams for IBM Cloud®](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-templatesmessagehub-events-template) When new data is added in an IBM® Event Streams for IBM Cloud® topic, log the change in the console. <br><br> * Node.js 10<br> * Node.js 12<br> * Python 3<br> * PHP 7<br><br><br> [Code](https://github.com/ibm-functions/template-messagehub-trigger) 
 [Periodic Slack Reminder](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-templatesslack-reminder-template) Use a webhook to Slack based on a periodic trigger. <br><br> * Node.js 10<br> * Node.js 12<br> * Python 3<br> * PHP 7<br><br><br> [Code](https://github.com/ibm-functions/template-reminder-slack) 







 Deploying the IBM Cloudant Events template 

The IBM Cloudant template creates a sequence of actions and a trigger that invokes that sequence. The trigger is fired when a change is made in the connected IBM Cloudant example database.
API & SDK reference library

Filter:

Type



1. Service
2. Software



Categories



1.
AI / Machine Learning
2.
Analytics
3. Blockchain
4.
Compute
5.
Containers
6.
Databases
7.
Developer tools
8. Integration
9.
Internal
10.
Logging and monitoring
11. Mobile
12.
Networking
13.
Platform
14.
Security
15.
Storage
Most online data sources provide self-referencing public URLs for objects in the store to support direct access. If you add a URL, it must be valid and reachable. If it is not, the Slack integration doesn't include the URL in its response and the Facebook integration doesn't return any response.

The Facebook and Slack integrations can successfully display the search result response when the URL field is empty.



You must use a field for at least one of the search results.

If no options are available from the drop-down fields, give Discovery more time to finish creating the collection. If the collection is not created, then your collection might not contain any documents or might have ingestion errors that you need to address first.

![Shows that the Title, Shortdesc, and url fields are selected and the preview search card is populated with information from those fields](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/search-configure-fields.png)

As you add field mappings, a preview of the search result is displayed with information from the corresponding fields of your data collection. This preview shows you what gets included in the search result response that is returned to users.

To get help with configuring the search, see [Troubleshooting](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-addsearch-add-troubleshoot).
3. Use the Message, No results found and Connectivity issue tabs to customize different messages to share with users based on the successfulness of the search.



Search result messages

 Tab Scenario Example message 

 Message Search results are returned I found this information that might be helpful: 
 No results found No search results are found I searched my knowledge base for information that might address your query, but did not find anything useful to share. 
 Connectivity issue I was unable to complete the search for some reason I might have information that could help address your query, but am unable to search my knowledge base at the moment. 



4.
viewResult, response, err := service.PostPartitionView(postPartitionViewOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(viewResult, "", " ")
fmt.Println(string(b))

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

All Go examples require the service object to be initialized. For more information, see the API documentation's [Authentication section](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration) for examples.

See the example (abbreviated) response, returning the full document for each appliance that matches a provided key:

{
"total_rows": 4,
"offset": 1,
"rows": [
{
"id": "small-appliances:1000043",
"key": "1000043",
"value":
"Bar",
"Pro",
"A professional, high powered innovative tool with a sleek design and outstanding performance"
],
"doc": {
"_id": "small-appliances:1000043",
"_rev": "2-b595c929aabc3ab13415cd0cc03e665d",
"type": "product",
"taxonomy":
"Home",
"Kitchen",
"Small Appliances"
],
"keywords":
"Bar",
"Blender",
"Kitchen"
],
"productId": "1000043",
"brand": "Bar",
"name": "Pro",
"description": "A professional, high powered innovative tool with a sleek design and outstanding performance",
* [Create a Golang action made up of multiple packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_go_multi_packages)
* [Create an action by using external libraries with Go modules](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_go_external_libraries)



* [Preparing Swift apps](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_swift)



* [Structuring Swift code](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_swift_struc)
* [Packaging a Swift 4.2 file](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_swift42_single)
* [Packaging Swift 4.2 multi-file projects and dependencies](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_swift42_multi)



* [Preparing Ruby apps](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_ruby)



* [Structuring Ruby code](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_ruby_struct)
* [Packaging Ruby code](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_ruby_pkg)



* [Preparing PHP apps](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_php)



* [Structuring PHP code](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_php_struct)
"name": "Schematic Dev Workspace",
  "type": [
    "terraform_v0.13.7"
  ],
  "location": "us-south",
  "description": "Schematic Dev Workspace",
  "tags": [],
  "template_repo": {
    "url": "<GitHub repo URL>",
    "githubtoken": "<github-token>"
  }



 Example Python request for schematics_variables_update.py file 

The following Python example request is for the example file, schematics_variables_update.py.

import logging, os, json

logging.basicConfig()
logging.root.setLevel(logging.NOTSET)
logging.basicConfig(level=logging.NOTSET)

from schematics_env_class import HPCCEnvironmentValues

logging.info("Schematic Variable Update Started")

if __name__ == '__main__':

    json_files = os.path.join(os.path.abspath("."), "config.json")

    with open(json_files, "r") as file:
        config_data = json.load(file)

    api_key = config_data["template_data"]["variablestore"]["value"]

    schematic_obj = HPCCEnvironmentValues(api_key)

    workspace_response = schematic_obj.schematics_service.get_workspace(w_id="<workspace id>").get_result()
    schematic_obj.update_variables(w_id="<workspace id>", 
        t_id=workspace_response["template_data"]["id"], 
        variablestore=config_data["template_data"]["variablestore"]
    )
You give Move2Kube the path to the source directory that contains the source code and the manifest files of the IBM Cloud Foundry application by using the -s flag.

Move the ./m2k_collect_cf directory into the enterprise-app/src directory using the following command:

mv m2k_collect move2kube-demos/samples/enterprise-app/src

Stay in the current working directory (move2kube-demos-<name_of_target>) that you moved m2k_collect from. Do not make enterprise-app/src directory your current working directory when running the remaining move2kube commands.

You should now have m2k_collect in the enterprise-app/src directory.

Invoke move2kube plan to create a plan for the enterprise-app by specifying the enterprise-app source directory with -s flag.

move2kube plan -s move2kube-demos/samples/enterprise-app/src

The following is an example of the returned output:

INFO[0000] Configuration loading done
INFO[0000] Start planning
INFO[0000] Planning started on the base directory
INFO[0000] [CloudFoundry] Planning
INFO[0000] Identified 5 named services and 0 to-be-named services
INFO[0000] [CloudFoundry] Done
INFO[0000] [ComposeAnalyser] Planning
INFO[0000] [ComposeAnalyser] Done
INFO[0000] [DockerfileDetector] Planning
INFO[0001] [DockerfileDetector] Done
INFO[0001] [Base Directory] Identified 5 named services and 0 to-be-named services
INFO[0001] Planning finished on the base directory
INFO[0001] Planning started on its sub directories
INFO[0001] Identified 1 named services and 0 to-be-named services in customers
INFO[0001] Identified 1 named services and 0 to-be-named services in frontend
INFO[0001] Identified 1 named services and 0 to-be-named services in gateway
INFO[0001] Identified 1 named services and 0 to-be-named services in inventory
* [Creating actions from the console](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_create_ui)
* [Creating actions from binaries](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_create_binaries)
* [Updating code or runtimes in actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_update)



* [Updating actions from the CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_update_cli)
* [Updating actions from the console](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_update_console)



* [Binding parameters to actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_params)
* [Packaging actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_pkgs)
* [Binding parameters to packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_pkgs_params)
* [Sharing packages of actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_pkgs_share)
* [Environment variables for actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_envvars)



* [Incorporating action environment variables in your app](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_envvars_app)
: Read the [release notes](https://github.com/IBM/continuous-delivery-go-sdk/blob/main/RELEASE_NOTES.md012-2022-09-09-beta) .





 16 September 2022 

Continuous Delivery service instances and toolchains that reside in Cloud Foundry orgs are no longer supported.
: Services instances and toolchains that reside in resource groups remain fully supported.





 08 September 2022 

Git Repos and Issue Tracking
: Upgraded to [GitLab 15.1.6](https://about.gitlab.com/releases/2022/08/30/critical-security-release-gitlab-15-3-2-released/).





 22 July 2022 

The Beta Terraform resources and data sources, Go SDKs, and HTTP APIs are now available for working with Toolchains and Tekton Pipelines.
: Terraform resources and data sources: [IBM-Cloud provider](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest).
: Go SDKs: Open-source repository (repo) [continuous-delivery-go-sdk](https://github.com/IBM/continuous-delivery-go-sdk).
: HTTP APIs: [Continuous Delivery Toolchain](https://cloud.ibm.com/apidocs/toolchain) and [Continuous Delivery Tekton Pipeline](https://cloud.ibm.com/apidocs/tekton-pipeline).

Ask questions and provide feedback in the

[#ask-your-question](https://ibm-devops-services.slack.com/archives/C5AHRCLHH) Slack channel.





 20 July 2022 

Git Repos and Issue Tracking
: Upgraded to [GitLab 15.0.4](https://about.gitlab.com/releases/2022/06/30/critical-security-release-gitlab-15-1-1-released/).





 12 July 2022 

Git Repos and Issue Tracking
Select a dictionary, and then click Upload. After you upload a dictionary, select it to view the dictionary and associate it with an entity type.



You can upload a ZIP file that contains a dictionary that you downloaded from another Knowledge Studio workspace. You must upload the type system that was downloaded from the other workspace in JSON format before you can upload the corresponding dictionary file. You can edit and add entries to a dictionary that you reuse from another Knowledge Studio workspace. See [Uploading resources from another workspace](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-exportimport) for more details.

Uploading a CSV file is also supported, but uploading it directly as a dictionary creates a preview-only dictionary that you cannot edit or use to pre-annotate documents. To upload a CSV file that you can edit and use for pre-annotation, click Create Dictionary to first create an empty dictionary, and then upload the CSV content as entries to that newly created dictionary.



* Click the Create Dictionary button to create an empty dictionary to which you can subsequently add dictionary entries. Specify a descriptive name for the dictionary, and then click Save.



3. To add entries to the dictionary, perform one of the following tasks:



* Click Add Entry to add a dictionary entry. Specify the lemma (the most representative word form for the term).
* Click Upload to upload a CSV file that contains dictionary entries, and then browse to select the file. The CSV file must be smaller than 1MB.



4. After uploading or adding entries, you can edit the entries.

Open an entry to specify equivalent terms, called surface forms. Each surface form must be 256 or fewer characters in length. You can change which of the surface forms is used as the lemma. For example, the lemma IBM might have surface forms like IBM Corp. and International Business Machines, Inc..
5. Select the appropriate part of speech for each lemma and surface form in the dictionary.

The part of speech information is used by the tokenizer, and during pre-annotation.
json_files = os.path.join(os.path.abspath("."), "config.json")

    with open(json_files, "r") as file:
        config_data = json.load(file)

    api_key = config_data["template_data"]["variablestore"]["value"]

    schematic_obj = HPCCEnvironmentValues(api_key)

    workspace_response = schematic_obj.schematics_service.get_workspace(w_id="<workspace id>").get_result()
    schematic_obj.update_variables(w_id="<workspace id>", 
        t_id=workspace_response["template_data"]["id"], 
        variablestore=config_data["template_data"]["variablestore"]
    )

logging.info("Schematic Variable Update Completed")
Show more





 Example Python request for schematics_env_class.py file 

import json
import logging

from ibm_cloud_sdk_core.authenticators import IAMAuthenticator
from ibm_schematics import SchematicsV1

class HPCCEnvironmentValues:

    def __init__(self, api_key):
        """
        create schematic services
        """
        self.authenticator = IAMAuthenticator(api_key)
        self.schematics_service = SchematicsV1(authenticator=self.authenticator)

        self.schematics_service.set_service_url('https://us.schematics.cloud.ibm.com')
        logging.info("Schematic Services created")

    def update_variables(self, w_id, t_id, variablestore):

        print("Function Schematic Update Variables Started")
[Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/deploy-workload/ready-to-complete.png)
7. Your content library should appear in the list of libraries. Once your content library has been created the next step is to upload images to the library. To import an operating system .iso image, click on the name of the library and then Actions > Import item.

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/deploy-workload/content-libraries.png)

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/deploy-workload/import-iso.png)
8. The import library item wizard will appear. Enter the URL of the .iso image you wish to import. To make things easier without requiring full network connectivity to the Internet or an on-premise share, the IBM Cloud internal mirrors can be leveraged. In the example below, the Rocky Linux 8.4 minimal ISO has been input.

Note: The following URLs will only work from within the IBM Cloud Private Network.
![subbucket.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/subbucket.png)
7. Click Run to see your chart.
8. Click Save and give your chart a name API Calls by App.
9. To see your visualization in context, add it to the Subscriber dashboard.



![apichartfinal.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/apichartfinal.png)

There is other information available for visualizing details about API calls, callers, and so on. A full list of API events is available in the API Connect Knowledge Center, or in the list of Terms when you create visualizations.





 Conclusion 

The ability to visualize API analytics in different styles and combinations gives you an opportunity to draw conclusions or go deeper into your API data. You can use this insight to make decisions about which APIs to offer, when to replace or retire an API, who is consuming your APIs, and so on.

For example, APIs version 1 (v1) and version 2 (v2) from a provider named "ACME" have been running for several years. They deprecated v1 when they released v2. They also ensured that existing v1 consumers were aware that they had a certain timeline to move to v2. As this deadline approaches, ACME wants to see how quickly consumers are moving off v1, so they can offer assistance to valued partners.

Using a visualization similar to the one we just built, ACME has this information available at a glance.

In this tutorial, we walked through a number of activities to help you create useful combinations of API and consumer data.
LOCATION cos://ALIAS NAME/mybucket/countriescapitals.parquet

Parameter values:
ALIAS NAME: The data engine endpoint for your region. For more information on the currently supported data engine endpoints, see [Data engine endpoints](https://cloud.ibm.com/docs/sql-query?topic=sql-query-overviewendpoints). Make sure that you select the standard aliases.

- Programmatically from within your PySpark application by using the following code snippet for PySpark called create_table_data_engine.py:

Example
: Enter:
 {: codeblock}
import requests
import time
def create_data_engine_table(api_key,crn):
    headers = {
    'Authorization': 'Basic Yng6Yng=',
    }
    data = {
    'apikey': api_key,
    'grant_type': 'urn:ibm:params:oauth:grant-type:apikey',
    }
    response = requests.post('https://iam.cloud.ibm.com/identity/token', headers=headers, data=data)
    token = response.json()['access_token']

    headers_token = {
    'Accept': 'application/json',
    'Authorization': f"Bearer {token}",
    }
    params = {
    'instance_crn': crn,
    }
    json_data = {
    'statement': 'CREATE TABLE COUNTRIESCAPITALS (Country string,Capital string) USING PARQUET LOCATION cos://ALIAS NAME/mybucket/countriescapitals.parquet',
    }
    response = requests.post('https://api.dataengine.cloud.ibm.com/v3/sql_jobs', params=params, headers=headers_token, json=json_data)
    job_id = response.json()['job_id']
    time.sleep(10)