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

GNU GENERAL PUBLIC LICENSE, VERSION 2

The Program includes some or all of the following licensed to you as
Separately Licensed Code under the GNU General Public License. For copies
of the source code for this software, send an email to <agupta@ca.ibm.com>
identifying the IBM product and the GPL-licensed program for which you
are requesting the source code

NULLMAILER, PYTHON-MELD3 DEBIAN PACKAGING [python-meld3], DEBIAN
[nullmailer], OPENRC-RUN [github.com/docker/docker], SUPERVISOR

END OF GNU GENERAL PUBLIC LICENSE, VERSION 2 NON-IBM-LICENSE INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

GNU GENERAL PUBLIC LICENSE, VERSION 3

The Program includes some or all of the following licensed to you as
Separately Licensed Code under the GNU General Public License. For copies
of the source code for this software, send an email to <agupta@ca.ibm.com>
identifying the IBM product and the GPL-licensed program for which you
are requesting the source code

GO-ETHEREUM [github.com/Zilliqa/gozilliqa-sdk],
GITHUB.COM/ZILLIQA/GOZILLIQA-SDK

END OF GNU GENERAL PUBLIC LICENSE, VERSION 3 NON-IBM-LICENSE INFORMATION
ibmcloud ce fn create -n nodejoke -runtime nodejs-18 --build-source GITHUB_DIR
4. Invoke your Function by pasting the provided URL into a web browser. Your browser displays a random joke!



For more information about the fn create command and its options, see [Create a Function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create).





 Including modules for a Python Function 

Create a function that includes a dependency for a specific Python module by creating a requirements.txt file. In this case, both the source code and requirements file are located in the same folder.



1. Create your Function by saving your code into a __main__.py file

import pyjokes
def main(params):
return {
"headers": { 'Content-Type': 'text/plain;charset=utf-8' },
"body": pyjokes.get_joke()
}
2. Create a requirements.txt containing your required dependencies for your Function

pyjokes==0.6.0
3. Create your files as a Function in Code Engine. Both of previous files must be accessible in the repository. If they are in a private repository, create [private code repository access](https://cloud.ibm.com/docs/codeengine?topic=codeengine-code-repositories) and then provide that value with the --build-git-repo-secret option. If your files are located in a directory other than main, provide the path to the directory with the --build-context-dir option.

ibmcloud ce fn create -n pyjokes -runtime python-3.11 --build-source GITHUB_DIR
4. Invoke your Function by pasting the provided URL into a web browser. Your browser displays a random joke!
ibmcloud ce application create --name tutorial-app --image <your_docker_ID>/tutorial

Example output

Creating application 'tutorial-app'...
[...]





 Next steps for buildpacks 

For more information, see [Deploying applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads).

Does your source code project use Dockerfile? Follow the same steps, but specify the Dockerfile build strategy to build an image for your application or job. For more information about Dockerfile, see [Writing a Dockerfile for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-dockerfile).

Looking for more code examples? Check out the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine).
Part 2: Set up a CI toolchain for Infrastructure as Code (Terraform) 

This tutorial is part 2 of a 3-part tutorial series where you learn IBM Cloud® DevSecOps best practices by using a complete reference implementation that is available as a service and powered by IBM Cloud continuous delivery. In part 2 of this tutorial series, you use the toolchain template for continuous integration (CI) with security and compliance-related best practices in DevSecOps for Terraform. It is preconfigured for continuous deployment with inventory integration, change management with Git Repos and Issue Tracking, evidence collection, and deployment of the infrastructure to IBM Cloud.



 Before you begin 

Before you begin part 2 of this tutorial series, ensure that you complete the following prerequisites:



1. Complete [Part 1: Set up prerequisites](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac).
2. View the [Getting started with DevSecOps in IBM Cloud - Part 1](https://video.ibm.com/embed/recorded/130714354) video.
3. Start the [IBM Cloud console](https://cloud.ibm.com/). The console is the starting point of this tutorial.







 Continuous Integration (CI) toolchain for Infrastructure as Code (IaC) introduction 

The CI toolchain implements the following best practices:



* Runs a static code scanner on the infrastructure code repositories and performs Terraform linting checks on the Infrastructure code.
* Runs compliance checks on the infrastructure code to detect secrets and security vulnerabilities.
* Builds artifacts on every Git commit.
* Stores the built artifacts metadata in inventory repository.
* Automatically builds and validates any code that is merged into the target Git repository branch.



Zoom

!
For a complete listing of options, see the [ibmcloud ce function create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create) command.

Before you begin



* Set up your [Code Engine CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli) environment.
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



This example uses a code file named main.js. You can use the following example code to create your main.js file or you can substitute your own code.

async function main(params) {
console.log(process.env);
console.log(params.__ce_headers);
console.log("params: "+params);
return {
statusCode: 200,
headers: { 'Content-Type': 'application/json' },
body: params };
}

module.exports.main = main;

Create your function and include the code in the command. For example, use the [ibmcloud ce function create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-function-create) command to create the myhellofun function.

ibmcloud ce fn create --name myhellofun --inline-code main.js --runtime nodejs-18

Example output

Creating function 'myhellofun'...
OK
Run 'ibmcloud ce function get -n myhellofun' to see more details.

https://myhellofun.glxo4kabcde.us-south.codeengine.appdomain.cloud

You can save the code that was used to create any inline function by running the function get command with the --save options.
* PAGE CONTENT TMPL.GO [golang.org/x/net (Copyright 2017 The Go Authors)](https://github.com/golang/net/blob/e18ecbb051101a46fc263334b127c89bc7bff7ea/http2/h2demo/tmpl.go)
* FOOTER (Copyright © OpenJS Foundation.) (codedrop-06072022/source/resource-catalog-cli.zip/resource-catalog-cli-d471ddd3d38302c9c93e27d8c62b242563d36c1c/vendor/github.com/fatih/color/Gopkg.lock), ICONS [github.com/smartystreets/goconvey (Not Required)](https://proxy.golang.org/github.com/smartystreets/goconvey/@v/v1.6.4.zip)







 Creative Commons Attribution 4.0 Non-IBM-License-Information 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by/4.0/legalcode](https://creativecommons.org/licenses/by/4.0/legalcode).



* SPDYSTREAM/DOCS [docker/spdystream](https://cloud.ibm.com/spdystream-449fdfce4d962303d702fec724ef0ad181c92528/README.md), FIXTURES [go-openapi/spec] (Not Required)
* DOCS [containerd/containerd (Not Required)](http://creativecommons.org/licenses/by/4.0/), EXPANDER_TEST.GO [go-openapi/spec (Not Required)](https://proxy.golang.org/github.com/go-openapi/spec/@v/v0.19.3.zip)
Text analysis with Code Engine 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

In this tutorial, you will learn about IBM Cloud® Code Engine by deploying a text analysis with Natural Language Understanding application. You will create a Code Engine project, select the project and deploy Code Engine entities - applications and jobs - to the project. You will learn how to bind IBM Cloud services to your Code Engine entities. You will also understand the auto-scaling capability of Code Engine where instances are scaled up or down (to zero) based on incoming workload.

IBM Cloud® Code Engine is a fully managed, serverless platform that runs your containerized workloads, including web apps, microservices, event-driven functions, or batch jobs. Code Engine even builds container images for you from your source code. Because these workloads are all hosted within the same Kubernetes infrastructure, all of them can seamlessly work together. The Code Engine experience is designed so that you can focus on writing code and not on the infrastructure that is needed to host it.

The platform is designed to address the needs of developers who just want their code to run. Code Engine abstracts the operational burden of building, deploying, and managing workloads in Kubernetes so that developers can focus on what matters most to them: the source code.



 Objectives 



* Understand IBM Cloud® Code Engine and how it simplifies the developer experience.
* Understand how easy it is to deploy and scale an application using Code Engine.
* Learn the use of jobs to execute run to completion workloads.



Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution54-code-engine/architecture_diagram.png)

Figure 1. Architecture diagram of the tutorial



1. Developer creates a Code Engine project and deploys a frontend and a backend Code Engine application.
vcr](https://github.com/dnaeon/go-vcr/archive/v1.0.1.zip), GO [Go](https://golang.org/dl/), HTTP2/H2DEMO/TMPL.GO [dns](https://pkg.go.dev/github.com/miekg/dns@v1.0.14), POLY [google.golang.org/api](https://proxy.golang.org/google.golang.org/api/@v/v0.9.0.zip), GOPHER IMAGE [Go](https://github.com/golang/go/releases/tag/go1.15.2), DIR.TMPL [golang.org/x/tools] (Not Required), SPRITES [golang.org/x/mobile](https://pkg.go.dev/golang.org/x/mobile), GOPHER [gonum](https://github.com/gonum/gonum/tree/3d26580ed485), RUNC-DOCUMENTATION [opencontainers/runc](https://github.com/opencontainers/runc/tree/v0.1.1)





 Creative Commons Attribution 4.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by/4.0/legalcode](https://creativecommons.org/licenses/by/4.0/legalcode)
Developing smart contracts with IBM Blockchain Platform Developer Tools 

Attention! The IBM Blockchain Platform Extension for VS Code (VS Code extension) referenced throughout the documentation is an open-source project which is no longer active, and therefore not officially supported by IBM. Refer to the [alternatives to the VS Code extension](https://github.com/IBM-Blockchain/blockchain-vscode-extension/issues/3159).

The IBM® Blockchain Platform Developer Tools provide an environment within Visual Studio Code for developing, packaging, and testing smart contracts. You can use the tools to create your smart contract project and get started developing your business logic. You can then use the tools to test your smart contract either on your local machine by using a preconfigured instance of Hyperledger Fabric, or by connecting to an IBM Blockchain Platform network, before you deploy the smart contract to the IBM Blockchain Platform. This tutorial describes how to install and use the Developer Tools.

The IBM Blockchain Platform extension works seamlessly with any instance of the IBM Blockchain Platform that uses Hyperledger Fabric versions 1.4 and later. This tutorial is oriented toward users of the high-level Fabric smart contract programming model. If you are using low-level smart contract APIs, you can find additional instructions in the [IBM Blockchain Platform extension documentation](https://github.com/IBM-Blockchain/blockchain-vscode-extension/blob/master/README.md). For more information, see the [Writing Your First Chaincode](https://hyperledger-fabric.readthedocs.io/en/latest/chaincode4ade.html) tutorial in the Fabric documentation.



 Before you begin 

Attention! The IBM Blockchain Platform Extension for VS Code (VS Code extension) referenced throughout the documentation is an open-source project which is no longer active, and therefore not officially supported by IBM. Refer to the [alternatives to the VS Code extension](https://github.com/IBM-Blockchain/blockchain-vscode-extension/issues/3159).





 Prerequisites
[Part 2: Set up a CI toolchain for Infrastructure as Code (Terraform)](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac-ci)Part 2: Set up a CI toolchain for Infrastructure as Code (Terraform)

This tutorial is part 2 of a 3-part tutorial series where you learn IBM Cloud® DevSecOps best practices by using a complete reference implementation that is available as a service and powered by IBM Cloud continuous delivery. In part 2 of this tutorial series, you use the toolchain template for continuous integration (CI) with security and compliance-related best practices in DevSecOps for Terraform. It is preconfigured for continuous deployment with inventory integration, change management with Git Repos and Issue Tracking, evidence collection, and deployment of the infrastructure to IBM Cloud.

Schematics Continuous Delivery

+1

DevSecOps



* 1 hour
* 2023-06-06



[Part 1: Set up prerequisites](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac)Part 1: Set up prerequisites

This tutorial is part 1 of a 3-part tutorial series where you learn IBM Cloud® DevSecOps best practices to develop Infrastructure as Code (IaC) (Terraform configuration) and deploy it by using a complete reference implementation that is available as a service and powered by IBM Cloud® Continuous Delivery. In part 1 of this tutorial series, you review some background information and set up prerequisites.

Schematics Continuous Delivery

+1

DevSecOps



* 1 hour
* 2023-01-13



[Part 1: Set up prerequisites](https://cloud.ibm.com/docs/devsecops?topic=devsecops-tutorial-cd-devsecops)Part 1: Set up prerequisites
In Composer, you can specify richer sequences by using source code rather than the command line.



 For JavaScript 

const composer = require('@ibm-functions/composer')

module.exports = composer.seq('action1', 'action2')





 For Python 

import composer

def main():
return composer.sequence('action1', 'action2')

Zoom

![Sequence with two actions.](https://cloud.ibm.com/docs-content/v1/content/adc643f3bedeea02b638bc1c34732852dcb40a45/openwhisk/images/composer-sequence.png)

Figure 1. Sequence with two actions

You aren't limited to chaining together functions in Composer. Composer includes a family of [JavaScript](https://github.com/ibm-functions/composer/blob/master/docs/COMBINATORS.md) or [Python](https://github.com/ibm-functions/composer-python/blob/master/docs/COMBINATORS.md) based combinators that enhance the expressiveness of sequences. You can see common examples in the following sections.







 Error handling for a sequence 

You can add error handling to a sequence by using try-catch-finally blocks. In this example, you surround the sequence with a try. The handleError code executes if either action returns an error.



 For JavaScript 

const composer = require('@ibm-functions/composer')

module.exports = composer.try(
composer.seq('action1', 'action2'),
'handleError')





 For Python 

import composer

def main():
return composer.do(composer.sequence('action1', 'action2'),
'handleError')

Zoom

![Sequence with error handling.]
Develop and deploy an app by using Code Engine 

In this tutorial, you learn how to create an open toolchain by using IBM Cloud® Continuous Delivery and deploy your app on [Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started). You also learn how toolchains are implemented in the Continuous Delivery service and how to develop and deploy a simple web application (app) by using toolchains.

IBM Cloud® Code Engine is a fully managed, serverless platform that runs your containerized workloads, including web apps, micro-services, event-driven functions, or batch jobs. Code Engine even builds container images for you from your source code. Because these workloads are all hosted within the same Kubernetes infrastructure, all of them can seamlessly work together. The Code Engine experience is designed so that you can focus on writing code and not on the infrastructure that is needed to host it.

The toolchain that is used in this tutorial implements standard DevOps practices such as code scanning, acceptance tests, Git repos, and continuous integration and continuous delivery capabilities. After you create clusters and associate them with a Continuous Delivery cluster group, you create a toolchain to change your app's code and push the change to the Git Repos and Issue Tracking repo. When you push changes to your repo, the Tekton-based delivery pipeline automatically builds and deploys the code.

[Tekton](https://www.ibm.com/cloud/blog/tekton-a-modern-approach-to-continuous-delivery) is an open source, vendor-neutral, Kubernetes-native framework that you can use to build, test, and deploy apps. Tekton provides a set of shared components for building [continuous integration](https://www.ibm.com/garage/method/practices/code/practice_continuous_integration/) and [continuous delivery](https://www.ibm.com/garage/method/practices/deliver/practice_continuous_delivery/) systems. As an open source project, Tekton is managed by the [Continuous Delivery Foundation](https://cd.foundation/).
Part 3: Set up a CD toolchain for Infrastructure as Code 

This tutorial is part 3 of a 3-part tutorial series where you learn IBM Cloud® DevSecOps best practices by using a complete reference implementation that is available as a service and powered by IBM Cloud® Continuous Delivery. In part 3 of this tutorial series, you use the toolchain template for continuous deployment (CD) with security and compliance-related best practices in DevSecOps.



 Before you begin 

Before you begin part 3 of this tutorial series, ensure that you complete the following prerequisites:



1. Complete [Part 1: Set up prerequisites](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac).
2. Complete [Part 2: Set up a CI toolchain for Infrastructure as Code (Terraform)](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-tutorial-iac-ci).
3. View the [Getting started with DevSecOps in IBM Cloud - Part 2](https://video.ibm.com/embed/recorded/130714358) video.







 CD - Deploy a secure app with DevSecOps practices 

The DevSecOps CD toolchain contains only one pipeline for continuous deployment. It implements the following best practices:



* Change Management automation to help developers, approvers, and auditors track deployments from the lens of compliance.
* Creates an evidence summary from the evidence that is collected in the CI pipeline.
* Creates a change request in Git Repos and Issue Tracking based change management repository and adds deployment evidence to it.
* Uses the inventory repository to promote built artifacts to deployment environments like staging and prod.
* Checks the CR, and auto approves if all checks pass.
* If CR is approved, or emergency, the toolchain deploys the image from the inventory to production.







 Guided setup overview for the CD toolchain 

Any of the methods in this tutorial takes you to the guided setup experience.
* TXT_VN [golang/text](https://github.com/golang/text/archive/v0.3.0.zip)
* IMAGES [jQuery-ui (Not Required)](http://jqueryui.com/resources/download/jquery-ui-1.10.3.zip)







 Creative Commons Attribution Share Alike 4.0 Generic 

The Program includes some or all of the following works licensed under the Creative Commons. The URL to the license is [https://creativecommons.org/licenses/by-sa/4.0/legalcode](https://creativecommons.org/licenses/by-sa/4.0/legalcode)



* README.MD [docker-ce-cli](https://github.com/docker/docker-ce/archive/v19.03.12.zip)
* GO-METRICS DOCS [docker-ce-cli](https://github.com/docker/docker-ce/archive/v19.03.12.zip), DOCS [go-digest](https://proxy.golang.org/github.com/opencontainers/go-digest/@v/v1.0.0-rc1.zip), GLOB LOGO [Glob](http://registry.npmjs.org/glob/-/glob-7.1.6.tgz)







 GNU General Public License, Version 2 

The Program includes some or all of the following licensed to you as Separately Licensed Code under the GNU General Public License. For copies of the source code for this software, send an email to [devlic@us.ibm.com](mailto:devlic@us.ibm.com) identifying the IBM product and the GPL-licensed program for which you are requesting the source code.



* DEBIAN-ARCHIVE-KEYRING
* DEFAULTER.JS [Adm-zip]
Code examples that use the CDN API 

This document contains example API calls and the resulting output for numerous CDN APIs.



 General steps that are needed for all API calls 

Before you begin, you must download and install the Soap Client from [https://github.com/softlayer/softlayer-api-php-client](https://github.com/softlayer/softlayer-api-php-client).



* You must get access to the SoapClient through vendor/autoload. The path is relative to where the script is run from and might need to be modified.

require_once __DIR__.'/vendor/autoload.php';
* All API calls are authenticated with your username and an apiKey. More information on how to generate an apiKey can be found on the [Softlayer API Getting Started](https://softlayer.github.io/article/getting-started/) page, under "Getting Your API Key".

$apiUsername = '<Your username>' ;
$apiKey = '<Your apiKey>' ;
* Initialize SoapClient for the appropriate class.







 Example code for listing vendors 

In this case, it is the SoftLayer_Network_CdnMarketplace_Vendor class, which defines the listVendors API and must be passed as a parameter to SoftLayerSoapClient::getClient(). You need the name of an active vendor later, when you create a Domain Mapping

$client = SoftLayerSoapClient::getClient('SoftLayer_Network_CdnMarketplace_Vendor', null, $apiUsername, $apiKey);
try {
$vendors = $client->listVendors();
print_r($vendors);
} catch (Exception $e) {
die('Unable to retrieve list of vendors: ' . $e->getMessage());
}

The listVendor code displays an array of vendors, their status, and features. The example output shows one active vendor, Akamai.

Array
(