vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [CVE-2021-3634](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3634)







 Change log for 1.11.1, released 31 August 2021 

Review the changes that are in version 1.11.1 of the managed Istio add-on.

Previous version
: 1.10.3

Current version
: 1.11.1

Updates in this version
: See the Istio release notes for [Istio 1.11.0](https://istio.io/latest/news/releases/1.11.x/announcing-1.11/) and [Istio 1.11.1](https://istio.io/latest/news/releases/1.11.x/announcing-1.11.1/.).
: Adds a postStart variable to the sidecar to enable the holdApplicationUntilProxyStarts option. Since the sidecar is normally last this doesn't impact default behavior where Istio places the sidecar as the last container. If you are adding containers to your pods, verify that they get added before the sidecar or can wait for the sidecar to start.
: Resolves the following CVEs



* [CVE-2021-22898](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22898)
* [CVE-2021-22924](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22924)
* [CVE-2021-22925](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22925)



: For more information, see the [Istio security bulletin 2021-008](https://istio.io/latest/news/security/istio-security-2021-008/).







 Version 1.10 (unsupported)
Key Management Service provider v2.5.12 v2.5.13 Updated Go dependencies and to Go version 1.19.4. Changed to focal distribution. 
 Konnectivity agent and server v0.0.33_418_iks v0.0.34_491_iks See the [Konnectivity release notes](https://github.com/kubernetes-sigs/apiserver-network-proxy/releases/tag/v0.0.34). 
 Kubernetes v1.25.5 v1.25.6 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.6). 







 Change log for worker node fix pack 1.25.6_1530, released 30 January 2023 

The following table shows the changes that are in the worker node fix pack 1.25.6_1530. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.25.5_1528

 Component Previous Current Description
"last_job": {
"command_object_id": "us-south.workspace.basic-resource-group.483b1ea2",
"command_name": "workspace_destroy",
"job_status": "job_finished"
},
"updated_at": "0001-01-01T00:00:00Z"
},
{
"command_object_id": "us-south.workspace.basic-cos-storage.535f45d6",
"command_object_name": "basic-cos-storage",
"source": {
"source_type": "git_hub",
"git": {
"git_repo_url": "https://github.com/Cloud-Schematics/blueprint-example-modules/tree/main/IBM-Storage",
"git_branch": "main"
},
"catalog": {},
"cos_bucket": {}
},
"inputs":
{
"name": "cos_instance_name",
"value": "$blueprint.cos_instance_name",
"metadata": {}
},
{
"name": "cos_single_site_loc",
"value": "ams03",
"metadata": {}
},
{
"name": "cos_storage_plan",
"value": "$blueprint.cos_storage_plan",
"metadata": {}
},
{
"name": "resource_group_id",
"value": "$module.basic-resource-group.outputs.resource_group_id",
"metadata": {}
}
],
"outputs":
{
"name": "cos_crn",
"metadata": {}
ibmcloud pi instance-capture INSTANCE_ID --destination DEST --name NAME [--volumes "VOLUME1 VOLUME2"] [--access-key KEY] [--secret-key KEY] [--region REGION] [--image-path TYPE]
2. Find your newly exported image by completing either one of the following tasks:



* To see your newly exported image in the image catalog, use the ibmcloud pi image-list-catalog command:

ibmcloud pi image-list-catalog [--long] [--json]
* To see your newly exported image in COS, use the ibmcloud cos list-objects command:

ibmcloud cos list-objects --bucket BUCKET_NAME [--delimiter DELIMITER] [--encoding-type METHOD] [--prefix PREFIX] [--starting-token TOKEN] [--page-size SIZE] [--max-items NUMBER] [--region REGION] [--json]
--file FILE
: Input through the file. File format Supported - JSON





 Example 

To update an environment with ID prodEnvironment using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac environment update --name Production_Environment --environment_id prodEnvironment --description sampleUpdatedDesc --tags sampleUpdatedTag --color_code "FF0000"



 Output 

The command returns the following output:

name Production_Environment
environment_id prodEnvironment
description sampleUpdatedDesc
tags sampleUpdatedTag
color_code FF0000
created_time 2021-05-21T05:28:07.000Z
updated_time 2021-05-21T05:33:00.000Z









 ibmcloud ac environment delete 

You can delete an environment, by using the command:

ibmcloud ac environment delete --environment_id ENVIRONMENT_ID



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID.





 Example 

To delete an environment with ID prodEnvironment, run the following command:

ibmcloud ac environment delete --environment_id prodEnvironment



 Output 

The command returns the following output:

OK









 ibmcloud ac collection list 

You can list all collections, by using the command:

ibmcloud ac collection list [--sort SORT] [--limit LIMIT] [--offset OFFSET] [--features FEATURES] [--properties PROPERTIES] [--tags TAGS] [--expand EXPAND] [--include INCLUDE]



 Command options 

--limit LIMIT (optional)
: Used for pagination. The number of records to retrieve.

--offset OFFSET (optional)
: Used for pagination. The number of records to skip.

--features FEATURES (optional)
curl -X GET "$vpc_api_endpoint/v1/images/$image_id/export_jobs?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token"





 Viewing image export job details by using the API 

To view the details of a specific image export job by using the API, use [Retrieve an image export job](https://cloud.ibm.com/apidocs/vpc/latestget-image-export-job).

For the$image_id variable, specify the ID of the custom image that was exported. For the $export_job_id variable, specify the ID of the image export job for which you want to retrieve details.

curl -X GET "$vpc_api_endpoint/v1/images/$image_id/export_jobs/$export_job_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token"





 Deleting or canceling an image export job by using the API 

To delete a completed image export job or cancel (and delete) an in-progress image export job by using the API, use [Delete an image export job](https://cloud.ibm.com/apidocs/vpc/latestdelete-image-export-job).

For the$image_id variable, specify the ID of the custom image for which you want to delete an export job. For the $export_job_id variable, specify the ID of the image export job that you want to delete.

curl -X DELETE "$vpc_api_endpoint/v1/images/$image_id/export_jobs/$export_job_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token"





 Renaming an image export job by using the API 

To rename a custom image export job by using the API, use [Update an image export job](https://cloud.ibm.com/apidocs/vpc/latestupdate-image-export-job).
--------------------







 ibmcloud is snapshot-delete 

Delete one or more snapshots.

ibmcloud is snapshot-delete (SNAPSHOT1 SNAPSHOT2 ...) [--output JSON] [-f, --force] [-q, --quiet]



 Command examples 



* ibmcloud is snapshot-delete my-snapshot
* ibmcloud is snapshot-delete r134-2fbe71a8-126e-4a05-80ad-dad45df491a5







 Command options 



* SNAPSHOT1: ID or Name of the snapshot.
* SNAPSHOT2: ID or Name of the snapshot.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is snapshot-update 

Update a snapshot.

ibmcloud is snapshot-update SNAPSHOT --name NEW_NAME [--tags TAG_NAME1,TAG_NAME2,...] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is snapshot-update 64bec87d-d175-4fa5-b240-b092fdbcedd6 --name my-snapshot --output JSON
* ibmcloud is snapshot-update cli-demo-snapshot-1 --name my-snapshot --output JSON
* ibmcloud is snapshot-update f8d51ab0-961f-4c23-8976-b1e48cc4f260 --name mysnapshot60 --tags env:tfp
: Optional: Do not show the message of the day or update reminders.



 Example cluster get command 

ibmcloud ks cluster get --cluster my_cluster --show-resources







 ibmcloud ks cluster image-security disable 

Virtual Private Cloud

Classic infrastructure

Disable [image security enforcement](https://cloud.ibm.com/docs/containers?topic=containers-imagesportieris-image-sec). When you disable the feature, the underlying ClusterImagePolicy CRD is removed, which removes all the default image policies and any custom images policies that you created.

ibmcloud ks cluster image-security disable --cluster CLUSTER [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster image-security disable command 

ibmcloud ks cluster image-security disable --cluster my_cluster







 ibmcloud ks cluster image-security enable 

Virtual Private Cloud

Classic infrastructure

Enable [image security enforcement](https://cloud.ibm.com/docs/containers?topic=containers-imagesportieris-image-sec) by installing the Portieris Kubernetes admission controller and the associated default image policies in your cluster.

ibmcloud ks cluster image-security enable --cluster CLUSTER [-f] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-f
: Optional: Force the command to run with no user prompts.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster image-security enable command 

ibmcloud ks cluster image-security enable --cluster my_cluster







 ibmcloud ks cluster ls 

Virtual Private Cloud

Classic infrastructure

Satellite
curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/json" --header "Accept: audio/wav" --data "{"text":"hello world"}" --output hello_world.wav "{url}/v1/synthesize?voice=en-AU_CraigVoice"

The following example replaces the obsolete voice with the Australian English voice en-AU_JackExpressive:

curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/json" --header "Accept: audio/wav" --data "{"text":"hello world"}" --output hello_world.wav "{url}/v1/synthesize?voice=en-AU_JackExpressive"

Repeat this substitution for each use of an obsolete voice in your application.





 Step 3: Update any custom models that are based on the neural voices 

If you used custom models to create a dictionary of custom words for your neural voices, you need to verify that the custom words work properly with the enhanced neural or expressive neural voices. At a minimum, you need to compare the phonetic symbols that you used with custom words for neural voices with the symbols that are available for the enhanced neural and expressive neural voices. Table 2 provides links to the topics that provide the phonetic symbols for the obsolete neural voices and for the enhanced neural and expressive neural voices.



Table 2. Phonetic symbols for obsolete neural voices and for enhanced neural and expressive neural voices

 Language Phonetic symbols for obsolete neural voices Phonetic symbols for enhanced neural and expressive neural voices 

 Australian English [English (Australian) symbols (obsolete)](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-auSymbols) [English (Australian) symbols](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-auSymbols-new)
: Collections array.

--file FILE
: Input through the file. File format Supported - JSON.





 Example 

To update description a feature with ID ibm-discount using flags ([click here](https://cloud.ibm.com/docs/cli?topic=cli-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac feature update --environment_id "production" --name "Indian IBMers" --feature_id "ibm-discount" --description "Discount given to IBM Indian employees" --enabled_value true --disabled_value false --segment_rules '[{"rules":{"segments":"ibm_employees"]}],"value": true,"order": 1}]' --collections '[{"collection_id":"corporatediscount","enabled": true}]' --tags "discount,sale" --enabled true



 Output 

The command returns the following output:

updated_time 2021-02-02T18:06:03Z
description Discount given to IBM Indian employees
enabled_value true
disabled_value false
segment_rules <Array>
created_time 2021-02-02T17:52:46Z
name Indian IBMers
type BOOLEAN
enabled true
collections <Array>









 ibmcloud ac feature update-values 

You can update values of a feature (This method allows the update of feature name, feature enabled_value, feature disabled_value, tags, description, and feature segment rules, however this method does not allow toggling the feature flag and assigning feature to a collection.), by using the command:

ibmcloud ac feature update-values {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --tags TAGS --segment_rules SEGMENT_RULES}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
: Feature name.
: Expanded view of the collection details.

--include INCLUDE (optional)
: Include feature and property details in the response.





 Example 

To get a collection with ID sampleId, run the following command:

ibmcloud ac collection get --collection_id sampleId



 Output 

The command returns the following output:

name sample
collection_id sampleId









 ibmcloud ac collection update 

You can update a collection, by using the command:

ibmcloud ac collection update {--file FILE-PATH | --name NAME --collection_id COLLECTION_ID --description DESCRIPTION --tags TAGS}



 Command options 

--collection_id COLLECTION_ID
: Collection ID. Required field - input either as a flag or from file.

--name NAME
: Collection name. Required field - input either as a flag or from file.

--description DESCRIPTION
: Description of the collection. Required field - input either as a flag or from file.

--tags TAGS (optional) File format Supported
: Tags associated with the collection. Required field - input either as a flag or from file.

--file FILE
: Input from the file. File format Supported - JSON





 Example 

To update a collection with ID sampleId using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac collection update --collection_id sampleId --name sample --description sampleDesc --tags sampleTag



 Output 

The command returns the following output:

name sample
collection_id sampleId
description sampleDescUpdated
created_time 2021-01-18T08:15:45Z
updated_time 2021-01-19T05:57:27Z









 ibmcloud ac collection delete 

You can delete a collection, by using the command:

ibmcloud ac collection delete --collection_id COLLECTION_ID



 Command options
ibmcloud is image-export-jobs IMAGE

The following example shows the export job history for a custom image with the ID of 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479.

ibmcloud is image-export-jobs 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479

For more information, see [ibmcloud is image-export-jobs](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referenceimage-export-jobs) in the VPC CLI reference page.





 Viewing image export job details by using the CLI 

To view the details of a specific image export job by using the CLI, use the ibmcloud is image-export-job command. Specify the name or ID of the custom image that was exported by using the IMAGE variable. Specify the name or ID of the image export job by using the JOB variable.

ibmcloud is image-export-job IMAGE JOB

For more information, see [ibmcloud is image-export-job](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referenceimage-export-job) in the VPC CLI reference page.





 Deleting or canceling an image export job by using the CLI 

To delete a completed image export job or cancel (and delete) an in-progress image export job, use the ibmcloud is image-export-job-delete command. Specify the name or ID of the custom image that was exported by using the IMAGE variable. Specify the name or ID of the image export job by using the JOB variable.

ibmcloud is image-export-job-delete IMAGE JOB

For more information, see [ibmcloud is image-export-job-delete](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceimage-export-job-delete) in the VPC CLI reference page.
See [Replacing a slot context variable value](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-found-handler-event-properties) for a usage example for this property and the event.previous_value property. 
 event.previous_value Previous value of the context variable for this slot. 
 has_skipped_slots True if any of the slots or slot handlers that are configured with a next step option that skips slots was processed. See [Adding conditions to Found and Not found responses](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsslot-handler-next-steps) for more information about next step options for slots and [Handling requests to exit a process](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-node-level-handler) for information about next step options for slot handlers. 
 slot_in_focus Forces the slot condition to be applied to the current slot only. See [Getting confirmation](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-get-confirmation) for more details. You can use this property to collect and store the exact words that are submitted by a customer. See [Collecting summary information from the customer](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-get-confirmation). 



Consider using these approaches for handling common tasks.



* [Asking for everything at once](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-prompt-for-everything)
* [Capturing multiple values](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-multiple-entity-values)
* [Reformatting values](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-slotsdialog-slots-reformat-values)
See [Replacing a slot context variable value](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-found-handler-event-properties) for a usage example for this property and the event.previous_value property. 
 event.previous_value Previous value of the context variable for this slot. 
 has_skipped_slots True if any of the slots or slot handlers that are configured with a next step option that skips slots was processed. See [Adding conditions to Found and Not found responses](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsslot-handler-next-steps) for more information about next step options for slots and [Handling requests to exit a process](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-node-level-handler) for information about next step options for slot handlers. 
 slot_in_focus Forces the slot condition to be applied to the current slot only. See [Getting confirmation](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-get-confirmation) for more details. 



Consider using these approaches for handling common tasks.



* [Asking for everything at once](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-prompt-for-everything)
* [Capturing multiple values](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-multiple-entity-values)
* [Reformatting values](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-reformat-values)
* [Dealing with zeros](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-slotsdialog-slots-zero)
show the rotation policy for this key

ibmcloud kp key policies 4d5540bd-3235-4a46-a8af-974f7ed6558a -r --output json

{
"createdBy": "user id ...<redacted>...",
"creationDate": "2022-12-02T00:50:11Z",
"crn": "crn:v1:bluemix:public:kms:us-south:a/e3e8fd14a61a49cda102faad15b06c09:5ecfe306-d4af-48c0-ab07-b5c5bc751534:policy:0ec7ad62-982d-45bb-895f-986d95015f5b",
"lastUpdateDate": "2022-12-02T00:51:38Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"enabled": true,
"interval_month": 2
}
}
---------------------------------------------------------------------------------------------------------------------------------------------------
Show more

 update the policy to three months

ibmcloud kp key policy-update rotation 4d5540bd-3235-4a46-a8af-974f7ed6558a -m 3 -e --output json

{
String shortDesc = "{shortDesc}";
ReplaceOfferingOptions replaceOptions = new ReplaceOfferingOptions.Builder().catalogIdentifier(catalogID).id(offeringID).offeringId(offeringID).label(label).shortDescription(shortDesc).rev(revision.rev()).build();
Response<Catalog> response = service.replaceOffering(replaceOptions).execute();
System.out.println(response.getResult());

catalogID = "{catalogID}"
offeringID = "{offeringID}"
revision = "{revision}"
shortDesc = "{shortDesc}"
response = self.service.replace_offering(catalog_identifier=catalogID, offering_id=offeringID, id=offeringID, rev=revision, label=label, short_description=shortDesc)
print(response)

catalogID := "{catalogID}"
offeringID := "{offeringID}"
label := "{label}"
shortDesc := "{shortDesc}"
revision := "{revision}"
updateOptions := service.NewReplaceOfferingOptions(catalogID, offeringID)
updateOptions.SetID(offeringID)
updateOptions.SetLabel(label)
updateOptions.SetShortDescription(shortDesc)
updateOptions.SetRev(revision)
_, response, _ := service.ReplaceOffering(updateOptions)
fmt.Println(response)

vcatalogID = "{catalogID}";
offeringID = "{offeringID}";
revision = "{revision}";
label = "{label}";
shortDesc = "{shortDesc}";
Transitions defined by the rules will no longer take place for new objects.

Note: Existing transition rules will be maintained for objects that were already written to the bucket before the rules were deleted.

Cloud IAM users must have at a minimum the Writer role to remove a lifecycle policy from a bucket.

Classic Infrastructure Users must have Owner permissions on the bucket to remove a lifecycle policy from a bucket.

This operation does not make use of additional operation specific headers, query parameters, or payload.

Syntax

DELETE https://{endpoint}/{bucket}?lifecycle path style
DELETE https://{bucket}.{endpoint}?lifecycle virtual host style

Examples

Sample Request

DELETE /images?lifecycle HTTP/1.1
Host: s3.us.cloud-object-storage.appdomain.cloud
Date: Wed, 7 Feb 2018 18:50:00 GMT
Authorization: authorization string

Sample Response

HTTP/1.1 204 No Content
Date: Wed, 7 Feb 2018 18:51:00 GMT
Connection: close



* Java
* Python
* Node



public DeleteBucketLifecycleConfigurationRequest(String bucketName)

response = client.delete_bucket_lifecycle(Bucket='string')

var params = {
Bucket: 'STRING_VALUE' /* required /
};
s3.deleteBucketLifecycle(params, function(err, data) {
if (err) console.log(err, err.stack); // an error occurred
else console.log(data); // successful response
});

--------------------





 Temporarily restore an archived object 

This implementation of the POST operation uses the restore query parameter to request temporary restoration of an archived object. The user must first restore an archived object before downloading or modifying the object. When restoring an object, the user must specify a period after which the temporary copy of the object will be deleted. The object maintains the storage class of the bucket.