vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Run the ZAP Proxy.
* Run the zap test scripts.



The ZAP proxy records the traffic and discovers the endpoints to scan. After the scans are finished, the proxy produces a report and generates issues the same way as in the ZAP API scan.

Set opt-in-dynamic-ui-scan to a nonempty value for ZAP API scans to run. To opt out, set this parameter to empty.



* Add your own dynamic scan code to the dynamic-scan custom stage in your .pipeline-config.yaml file for a custom implementation.



For more information about the ZAP API scan and ZAP UI scans, see [Configuring ZAP scans](https://cloud.ibm.com/docs/devsecops?topic=devsecops-zap-scans).







 Release to inventory 

Use the release to inventory user script stage to add artifacts to the inventory by using the cocoa inventory add CLI command. For more information about the command, see the topic for [cocoa inventory add](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-cliinventory-add).

If you want to skip the inventory update if there are problems in the pipeline, use the following environment variables to check the status of the pipeline. Check their status before updating the inventory:



* skip-inventory-update-on-failure Opt-in environment variable from pipeline to specify whether inventory update should be done.
* one-pipeline-status Is set to 1 if there is any stage failure in the pipeline run.



You can use the pipelinectl interface to access your repos and artifacts by using the list_repos, load_repo, list_artifacts, and load_artifact commands. For more information about the commands, see the [pipelinectl](https://cloud.ibm.com/docs/devsecops?topic=devsecops-devsecops-pipelinectl) documentation.





 Collecting compliance data on build 

When the pipeline runs successfully, you can collect information about the build.
10 November 2022 (Versions 4.0.x and 4.5.x) 

Known issue: Updated Network Policy needed for PostgreSQL operator
: Known issue: For Speech services version 4.0.x (not including version 4.0.0) and 4.5.x, if the PostgreSQL operator and the Speech services are installed in different namespaces, the PostgreSQL operator is not able to monitor the PostgreSQL operands for the Speech services. The operator is prevented from monitoring the operands by the Network Policy that is in place for the Speech services.

This problem does not prevent the PostgreSQL cluster from functioning properly. The cluster remains active and fully functional. However, the operator is not able to update the operands when you upgrade to new versions of the Speech services.

The solution for the problem is to create an additional Network Policy for the PostgreSQL operator, as shown in the following steps. You can perform the steps regardless of whether the PostgreSQL operator is installed in the same namespace as the Speech services or in a different namespace.



1. Log in as an administrator of the Red Hat® OpenShift® project where the Speech services are installed.
2. Enter the following command to update the Network Policy for the Speech services:

cat << EOF | oc apply -f -
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
labels:
app.kubernetes.io/component: stt
app.kubernetes.io/instance: {{ <custom-resource-name> }}
app.kubernetes.io/name: speech-to-text
release: {{ <custom-resource-name> }}
name: <custom-resource-name>-postgres-network-policy
namespace: {{ <cpd-instance-namespace> }}
spec:
ingress:
- from:
- namespaceSelector: {}
podSelector:
matchLabels:
echo "$(date +"%b %d %G %H:%M:%S"): Restarting $controllerPodName pod"
kubectl delete pod $controllerPodName -n kube-system &> /dev/null
error "$(date +"%b %d %G %H:%M:%S"): Error restarting $controllerPodName pod in kube-system namespace."

controllerPodStatus=
for i in {1..12}
do
sleep 5
controllerPodStatus=$(kubectl get pods -n kube-system | grep ibm-vpc-block-csi-controller | awk '{print $3}')
if [ "$controllerPodStatus" == "Running" ]]; then
echo "$(date +"%b %d %G %H:%M:%S"): VPC Block CSI Driver is now using ibm-cloud-credentials secret"
rm ibm-cloud-credentials.yaml
error "Error deleting ibm-cloud-credentials.yaml."
exit 0
fi
done

error "$(date +"%b %d %G %H:%M:%S"): Error - ibm-vpc-block-csi-controller is in $controllerPodStatus state"
}

main "$@"
Show more
2. Run the generate-secret.sh script and specify iam or pod-identity as the IBMCLOUD_AUTHTYPE and your PROFILE-ID or API-KEY.

Example command to run generate-secret.sh by using pod-identity with your trusted profiled ID.

sh ./generate-secret.sh pod-identity PROFILE-ID

Example command to run generate-secret.sh by using iam with an API key.

sh ./generate-secret.sh iam API-KEY
3. After the secret is created in your your cluster, disable and re-enable the add-on.

ibmcloud oc cluster addon disable vpc-block-csi-driver --cluster CLUSTER-ID
* Port max = 3389
* Source type = Any





2. Obtain the connection information you need to connect to the Windows VPC.



1. Click Virtual server instances.
2. Click the name of your Windows VPC instance. The instance details are displayed.
3. Under Encrypted password click Download RDP file. A file that can be used with Windows Remote Desktop will be downloaded.

If you are using another client to connect to your Windows VPC, you can still use the information contained in the RDP file to get the connection information for the VPC.



3. Connect to your Windows VPC using a remote desktop client and the RDP file information. Sign in with the User name of .Administrator and the decripted ssh key as the password.







 Install NXLog 

Follow these steps to install NXLog.

You will need to run as a Windows Administrator for all command prompt or PowerShell steps.



1. The [Chocolately package manager](https://chocolatey.org/) is used to install NXLog. Run one of the following if you do not have the package manager already installed.

From a Windows command prompt (cmd.exe):

powershell -command "Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))"

From a PowerShell prompt:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))
2. Run the following command in PowerShell to install NXLog Community Edition.
: This release of the buildpack supports IBM SDK for Node.js runtime versions: 0.10.45, 0.10.46, 0.12.14, 0.12.15, 4.4.6, 4.4.7, 6.2.1, and 6.2.2. The default is now 4.4.7.

This release includes an updated App Management proxy that supports federated logins.

Included are fixes for the following security vulnerabilities:



* [CVE-2016-1669](https://www.ibm.com/support/pages/node/283763)







 11 July 2016 

Updated ASP.NET Core buildpack v0.9-20160706-1603
: This version of the buildpack includes the following changes:



* This version of the buildpack supports the .NET CLI 1.0 Preview 2 build and .NET Core 1.0 RTM
* The buildpack continues to support .NET CLI 1.0 Preview 1 and .NET Core 1.0 RC2
* The default .NET CLI version to be installed is now 1.0.0-preview2-003121







 22 June 2016 

Updated Node.js buildpack v3.5-20160609-1608
: This release of the buildpack adds IBM SDK for Node.js runtime versions 4.4.5 and 6.2.0. The default becomes 4.4.5.

The release removes support for older runtime versions as announced in [IBM Cloud Node.js Buildpack v3.3 – FIPS mode and more](https://www.ibm.com/blogs/cloud-archive/2016/05/node-buildpack-update-fips-mode/). The buildpack now supports 0.10.44, 0.10.45, 0.12.13, 0.12.14, 4.4.4, 4.4.5, 6.1.0, and 6.2.0.
GPU device plug-in and installer eb3a259 e32d51c Updated images for [CVE-2019-6454](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6454). 
 IBM Cloud Provider v1.11.7-198 v1.11.8-219 Updated to support the Kubernetes 1.11.8 release. Fixed periodic connectivity problems for load balancers that set externalTrafficPolicy to local. Updated load balancer events to use the latest IBM Cloud documentation links. 
 IBM Cloud File Storage for Classic plug-in 342 344 Changed the base operating system for the image from Fedora to Alpine. Updated image for [CVE-2019-6486](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6486). 
 Key Management Service provider 122 136 Increased client timeout to IBM Key Protect for IBM Cloud. Updated image for [CVE-2019-6486](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6486). 
 Kubernetes v1.11.7 v1.11.8 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.11.8). Update resolves [CVE-2019-6486](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6486) and [CVE-2019-1002100](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1002100). 
 Kubernetes configuration N/A N/A Added ExperimentalCriticalPodAnnotation=true to the --feature-gates option.
.then((data) => {
if (data != null) {
console.log(Retrieving bucket lifecycle config from: ${bucketName});
console.log(JSON.stringify(data, null, 4));
}
else {
console.log(No lifecycle configuration for ${bucketName});
}
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}
Show more

SDK References



* [getBucketLifecycleConfiguration](https://ibm.github.io/ibm-cos-sdk-js/AWS/S3.html)







 Create a lifecycle configuration 

Detailed information about structuring the lifecycle configuration rules are available in the [API Reference](https://cloud.ibm.com/docs/services/cloud-object-storage/api-reference?topic=cloud-object-storage-compatibility-api-bucket-operationscompatibility-api-new-bucket)

function createLifecycleConfiguration(bucketName) {
//
var config = {
Rules: [{
Status: 'Enabled',
ID: '<policy-id>',
Filter: {
Prefix: ''
},
Transitions: {
Days: <number-of-days>,
StorageClass: 'GLACIER'
}]
}]
};

return cos.putBucketLifecycleConfiguration({
Bucket: bucketName,
LifecycleConfiguration: config
}).promise()
.then(() => {
console.log(Created bucket lifecycle config for: ${bucketName});
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}
Show more

Key Values
Release notes for Continuous Delivery 

Use these release notes to learn about the latest updates to IBM Cloud® Continuous Delivery that are grouped by date. Release notes are available for a minimum of three years.



 12 July 2023 

Git Repos and Issue Tracking
: Upgraded to [GitLab 15.11.11](https://about.gitlab.com/releases/2023/07/05/security-release-gitlab-16-1-2-released/).





 13 June 2023 

Git Repos and Issue Tracking
: Upgraded to [GitLab 15.10.8](https://about.gitlab.com/releases/2023/06/05/security-release-gitlab-16-0-2-released/).





 19 May 2023 

Git Repos and Issue Tracking
: Upgraded to [GitLab 15.9.8](https://about.gitlab.com/releases/2023/05/10/security-release-gitlab-15-11-3-released/).





 20 April 2023 

Continuous Delivery toolchains are now integrated with the IBM Cloud® Event Notifications service.
: [Enabling Event Notifications for toolchains](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-event-notifications-cd)





 10 April 2023 

Git Repos and Issue Tracking
: Upgraded to [GitLab 15.8.5](https://about.gitlab.com/releases/2023/03/30/security-release-gitlab-15-10-1-released/).





 21 February 2023 

Java, Node, and Python SDKs for toolchains and Tekton pipelines are now generally available.
: Java SDK: [github.com/IBM/continuous-delivery-java-sdk](https://github.com/IBM/continuous-delivery-java-sdk)
docker://us.icr.io/foo/bar@sha256:1234567812345678123456781234567812345678123456781234567812345678
docker://us.icr.io/baz/quux@sha256:1234567812345678123456781234567812345678123456781234567812345678
EOF





 cocoa locker attachment get < attachment-id > 

Retrieves an attachment that was previously uploaded with cocoa locker evidence add.

Options:

--org (Required) Owner of the evidence locker repo, defaults to EVIDENCE_LOCKER_REPO_OWNER
--repo (Required) Name of the evidence locker repo, defaults to EVIDENCE_LOCKER_REPO_NAME
--git-provider Git service provider ("github")
--version Show version number
--git-token-path Git token path to read the secret from
--git-api-url Github API url

Run the command to upload attachment:

$ cocoa locker evidence add --evidence-type-id com.ibm.unit_test --evidence-type-version 1.0 --details result=success --attachment path/to/junit.xml

Example output of attachment upload:

{
...
"attachments": {
"junit.xml": "5aa5555aa55aa55a555aa5a5aa555555aaaa5aa5aa5555a55a5aa5aa5a5aaaaa",
},
...
}

Run the command to retrieve the attachment:

cocoa locker attachment get 5aa5555aa55aa55a555aa5a5aa555555aaaa5aa5aa5555a55a5aa5aa5a5aaaaa





 cocoa locker check 

Checks the required configuration and settings of the locker.
[DevSecOps issues repository](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cd-issues-repo.png)

Figure 5. DevSecOps issues repository





 Pipeline Configuration 

The repository contains custom scripts to run pipeline tasks in the CD Pipeline (.pipeline-config.yaml). Refer to [hello-compliance-deployment](https://us-south.git.cloud.ibm.com/open-toolchain/hello-compliance-deployment) sample repository that contains some default configuration and scripts.

By default, the setup Clone deployment configuration from the sample repository. When the repository is cloned, you can customize configurations and scripts for pipeline runs.



* New repository name: Name of the IBM-hosted Git Repos and Issue Tracking repository that is created by the toolchain as your deployment configuration repository. The region of the repository remains the same as that of the toolchain. Choose a unique name for the new repository.



If you have a deployment configuration repo from an existing continuous deployment toolchain, select the Switch to advanced configuration to configure the same settings for this pipeline.

Zoom

![DevSecOps pipeline configuration](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-cd-pipeline-config.png)

Figure 6. DevSecOps pipeline configuration





 Secrets 

Several tools in this toolchain require secrets to access privileged resources. An IBM Cloud API key is an example of such a secret. All secrets must be stored securely in a secrets vault and then referenced as required by the toolchain.

With IBM Cloud, you can choose from various secrets management and data protection offerings that help you to protect your sensitive data and centralize your secret.
As noted earlier, the toolchain currently supports linking only to existing Git Repos and Issue Tracking repositories.



* New repository name: Name of the IBM-hosted Git Repos and Issue Tracking Repository that is created by the toolchain as your inventory repository. The region of the repository remains the same as that of the toolchain.







 Issues 

Issues about incidents that are captured during the build and deployment process are tracked in the repository.

Zoom

![DevSecOps Issues repository](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-ci-issues-repo.png)

Figure 6. DevSecOps Issues repository

The default behavior of the toolchain is to Create new issues repository that creates a new repository as IBM-hosted Git Repos and Issue Tracking Repository. In case you want to link an existing Issues Repository for the toolchain, you can choose Use existing issues repository option and provide it as input to Repository URL field. As noted earlier, the toolchain currently supports linking only to existing Git Repos and Issue Tracking repositories.



* New repository name: Name of the IBM-hosted Git Repos and Issue Tracking repo that is created by the toolchain as your inventory repository. The region of the repository remains the same as that of the toolchain.







 Secrets 

Several tools in this toolchain require secrets to access privileged resources. An IBM Cloud API key is an example of such a secret. All secrets must be stored securely in a secrets vault and then referenced as required by the toolchain.

The Secrets step specifies which secret vault integrations are added to your toolchain. Use the provided toggles to add or remove the vault integrations that you require. However, these can be configured in subsequent steps.
The primary drive on my bare metal server shows up as /dev/sdb. What is wrong? 

This problem can be caused by the IPMI's Virtual Disk taking up the /dev/sda slot. You can safely disable the primary drive by connecting to IPMIView and clicking the Virtual Media tab. Select Options > Disable and click Apply to make the change. When the Bare Metal Servers is restarted next, the primary drive displays /dev/sda.





 Why is the CPU speed wrong? 

If you log in to a server and notice that the speed of the processors is incorrect, this discrepancy might be caused by Enhanced Intel SpeedStep Technology (EIST). EIST is the Intel® name for dynamic frequency scaling technology. This technology is also called CPU throttling or bus slewing in older systems. Some AMD systems use similar technologies that are called Cool'N'Quiet or PowerNow!. Though these technologies are not all the same, they have the same goal, which is to reduce the power consumption and heat production when the processor is not under heavy use by slowing the CPU speed. When the server is back under load, they raise the clock speed as necessary.

If you want to know whether the Intel processor on your server supports SpeedStep, use the following procedure from the IBM Cloud® console:



1. Click Devices.





* Identify your server in the list.
* Click the server name to view Device Details.
* Locate the Hardware subsection to find the model number of your server's processors CPU speed.
* With the server processor model number, go to the [Intel Processor Finder](http://processorfinder.intel.com) and use this number to find more information about the processor and whether it supports Enhanced Intel SpeedStep Technology.



EIST is an established technology. It's not common that you need to turn off EIST. However, if you decide that you don't want to use this feature, open a support case with the Support Team to disable this feature. The server is restarted when you disable EIST.





 What if my bare metal server has out-of-date firmware?
The behavior of the command can be altered by using these flags:



* --dry-run: Adds nothing to the locker, but shows what would be added.
* --cache-mode: Similar to dry-run. Doesn't actually add the evidence to the locker, but adds the attachments (if any) to the locker. Shows the evidence that would be added.
* --format: controls the output format, id or json (id by default).



Run the command to save results for [detect-secrets](https://github.com/IBM/detect-secrets):

$ cocoa locker evidence add --evidence-type-id com.ibm.detect_secrets --evidence-type-version 1.0.0 --details result=success --asset https://github.ibm.com/foo/bar.gitaaaaaaaabbbbbbbbccccccccddddddddeeeeeeee

Run the command to save unit test results:

$ cocoa locker evidence add --evidence-type-id com.ibm.unit_test --evidence-type-version 1.0.0 --details failure --asset https://github.ibm.com/foo/bar.gitaaaaaaaabbbbbbbbccccccccddddddddeeeeeeee
--attachment path/to/results/junit.xml --issue https://github.ibm.com/foo/bar/issues/123





 cocoa locker evidence get < evidence-id > 

Retrieves a piece of evidence from the locker.

Options:

--org (Required) Owner of the evidence locker repo, defaults to EVIDENCE_LOCKER_REPO_OWNER
--repo (Required) Name of the evidence locker repo, defaults to EVIDENCE_LOCKER_REPO_NAME
--git-provider Git service provider ("github")
--version Show version number
--git-token-path Git token path to read the secret from
--git-api-url Github API url
--format Output format ("json", default: "json")
Git Repos and Issue Tracking
: Upgraded to [GitLab 15.6.3](https://about.gitlab.com/releases/2022/12/16/gitlab-15-6-3-released/).





 14 December 2022 

The Continuous Delivery service is now designated as IBM Cloud for Financial Services Validated.
: This designation does not apply to all of the tools that you can integrate into toolchains. For more information about which tool integrations and tools are designated as IBM Cloud for Financial Services Validated when they are used with Continuous Delivery toolchains, see [Understanding tool integrations with IBM Cloud for Financial Services](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations).
: For more information about IBM Cloud for Financial Services, see [IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services).





 7 December 2022 

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





 1 December 2022 

The Terraform resources and data sources, Go SDKs, and HTTP APIs for toolchains and Tekton pipelines are now generally available.
: Updates include a few breaking changes.
: The Terraform resources and data sources, Go SDKs, and HTTP APIs are now a generally available, fully supported feature.
: Read the [release notes](https://github.com/IBM/continuous-delivery-go-sdk/blob/main/RELEASE_NOTES.md).





 18 November 2022 

The Beta Terraform resources and data sources, Go SDKs, and HTTP APIs are updated, including several breaking changes.
: Read the [release notes](https://github.com/IBM/continuous-delivery-go-sdk/blob/main/RELEASE_NOTES.md).





 16 November 2022 

Git Repos and Issue Tracking
* [R0046: NTP issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0046)
* [R0047: Location health checking](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0047)
* [R0048: etcd backup failure](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0048)
* [R0049: Satellite Link IAM API key issue](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0049)
* [R0050, R0051: Satellite Link connector issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0050)
* [R0052: Ingress certificate generation issues](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0052)
* [R0056: Pod status stuck in terminating](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0056)
* [R0057: Outbound traffic to IAM is failing](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0057)
* [R0058: DNS registration is failing](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0058)
* [R0059: Outbound traffic to IBM Cloud Container Registry is failing.](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0059)
* [R0060: Outbound traffic to LaunchDarkly is failing.](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debugR0060)





 Locations