vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* --image-path: [DEPRECATED] Replaced by image-file-name, region and bucket. Path to image starting with service endpoint and ending with image file name.
* --os-type: Operating system contained in the image (rhel, sles, aix, ibmi). Required when importing a raw image.
* --disk-type: Type of disk storage (i.e. tier1, tier3).
* --storage-pool value: Storage pool where the image will be imported to (use "ibmcloud pi storage-pools" to see available storage pools). If --storage-pool is provided then --disk-type and --affinity-policy values cannot be specified.
* --affinity-policy value: Affinity policy for image. Valid values are "affinity" and "anti-affinity". If --storage-pool is provided then this cannot be specified.
* --affinity-instance value: PVM instance identifier or name to base image affinity policy against; required if "--affinity-policy affinity" is specified and --affinity-volume is not provided.
* --affinity-volume value: Volume identifier or name to base image affinity policy against; required if "--affinity-policy affinity" is specified and --affinity-instance is not provided.
* --anti-affinity-instances value: Space separated list of instance identifiers or names to base image anit-affinity policy against; required if "--affinity-policy anti-affinity" is specified and --anti-affinity-volumes is not provided
* --anti-affinity-volumes value: Space separated list of volume identifiers or names to base image anti-affinity policy against; required if "--affinity-policy anti-affinity" is specified and --anti-affinity-instances is not provided.
* --access-key: Cloud Object Storage HMAC access key.
* --secret-key: Cloud Object Storage HMAC secret key.
* --image-file-name: The image file name.
* --bucket-access value: Indicates the bucket access type (private or public). Private access requires access and secret keys. Default is private.
* [Reclamation commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation)



* [ibmcloud ce reclamation delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-delete)
* [ibmcloud ce reclamation get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-get)
* [ibmcloud ce reclamation list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-list)
* [ibmcloud ce reclamation restore](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-reclamation-restore)



* [Registry commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-registry)



* [ibmcloud ce registry create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-registry-create)
* [ibmcloud ce registry delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-registry-delete)
* [ibmcloud ce registry get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-registry-get)
* [ibmcloud ce registry list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-registry-list)
* [ibmcloud ce registry update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-registry-update)



* [Repo commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-repo)
Unsupported:kubectl expose removes --container-port and --generator options The kubectl expose command no longer supports the deprecated --container-port and --generator options. If your scripts rely on these options, update them. 
 Unsupported:kubectl run removes several options The kubectl run command no longer supports the deprecated --serviceaccount, --hostport, --requests and --limits options. If your scripts rely on these options, update them.
icr.io/mynamespace/myrepo@sha256:1d71e323557502cc78ee6c237331a09b0c33ba59c14e5f683da3b1c6218779cc 30 ppc64le

OK
2. If the image does exist in trash, you can restore it by running the following command.

ibmcloud cr image-restore icr.io/mynamespacemyrepo@sha256:1d71e323557502cc78ee6c237331a09b0c33ba59c14e5f683da3b1c6218779cc

You receive the following response:

Restoring digest 'icr.io/mynamespace/myrepo@sha256:1d71e323557502cc78ee6c237331a09b0c33ba59c14e5f683da3b1c6218779cc' ...

Successfully restored digest 'icr.io/mynamespace/myrepo@sha256:1d71e323557502cc78ee6c237331a09b0c33ba59c14e5f683da3b1c6218779cc'
Successfully restored tags: ppc64le

OK



* If you have a local copy of the image, you can push it back to the registry. For more information, see [Pushing Docker images to your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_&interface=uiregistry_images_pushing_namespace).
POST /va/api/v3/exempt/image/issue/{issueType}/{issueID} container-registry.exemption.manager container-registry.exemption.create 
 Delete an account-level exemption. DELETE /va/api/v3/exempt/image/issue/{issueType}/{issueID} container-registry.exemption.manager container-registry.exemption.delete 
 List resource exemptions. GET /va/api/v3/exempt/image/{resource} container-registry.exemption.list 
 Get details of a resource exemption. GET /va/api/v3/exempt/image/{resource}/issue/{issueType}/{issueID} container-registry.exemption.list 
 Create or update a resource exemption. POST /va/api/v3/exempt/image/{resource}/issue/{issueType}/{issueID} container-registry.exemption.manager container-registry.exemption.create 
 Delete a resource exemption. DELETE /va/api/v3/exempt/image/{resource}/issue/{issueType}/{issueID} container-registry.exemption.manager container-registry.exemption.delete 
 List the types of exemption. GET /va/api/v3/exempt/types 
 List all exemptions. GET /va/api/v3/exemptions/account container-registry.exemption.list 
 Delete all exemptions. POST /va/api/v3/exemptions/deleteAll container-registry.exemption.manager container-registry.exemption.delete 
 List image exemptions. GET /va/api/v3/exemptions/image/{resource} container-registry.exemption.list 
 List exemptions for images. POST /va/api/v3/exemptions/images container-registry.exemption.list
Push your images, see [Pushing Docker images to your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_pushing_namespace).



You can now use clusters to pull the images, see [Building containers from images](https://cloud.ibm.com/docs/containers?topic=containers-images).





 Removing tags from images in your private repository 

You can remove a [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag), or tags, from an image in your private IBM Cloud repository, and leave the underlying image and any other tags in place by using the [ibmcloud cr image-untag](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_untag) command.

If multiple tags exist for the same image [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) within a repository and you want to remove the underlying image and all its tags, see [Deleting images from your private IBM Cloud repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove).

To remove a tag, or tags, by using the CLI, complete the following steps:



1. Log in to IBM Cloud by running the ibmcloud login command.
2. To remove a tag, run the following command, where IMAGE is the name of the image that you want to remove, in the format repository:tag. If a tag is not specified in the image name, the command fails. You can delete the tags for multiple images by listing each private IBM Cloud registry path in the command with a space between each path.

ibmcloud cr image-untag IMAGE

To find the names of your images, run ibmcloud cr image-list. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag.
* [Set up the Red Hat OpenShift Container Platform build to push images to Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_rhosregistry_rhos_os_push)









 Adding images to your namespace 

[Adding images to your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_)



* [Pulling images from another registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_pulling_reg)
* [Pushing Docker images to your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_pushing_namespace)
* [Copying images between registries](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_copying)
* [Creating images that refer to a source image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_source)
* [Building Docker images to use them with your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_creating)
* [Pushing images by using an API key](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_api_key_push_image)
* [Removing tags from images in your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_untag)
* [Deleting images from your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove)



* [Deleting images from your private repository in the CLI](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove_cli)
One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is vpn-server-route-delete 

Delete one or more VPN routes.

ibmcloud is vpn-server-route-delete VPN_SERVER (ROUTE_ID1 ROUTE_ID2 ...) [--vpc VPC] [--output JSON] [-f, --force] [-q, --quiet]



 Command options 



* VPN_SERVER: ID or name of the VPN server.
* ROUTE_ID1: ID or name of the VPN route.
* ROUTE_ID2: ID or name of the VPN route.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* --force, -f: Force the operation without confirmation.
* -q, --quiet: Suppress verbose output.



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









 COMPUTE COMMANDS 

The following section provides information about CLI commands for compute functionality.





 Images 



 ibmcloud is operating-systems 

List all operating systems.

ibmcloud is operating-systems [--output JSON] [-q, --quiet]



 Command options 



* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is operating-system 

View details of an operating system.

ibmcloud is operating-system OPERATING_SYSTEM_NAME [--output JSON] [-q, --quiet]



 Command options 



* OPERATING_SYSTEM_NAME: Name of the operating system.
* To create an exemption for a security issue, run the [ibmcloud cr exemption-add](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_exemption_add) command.
* To list your exemptions for security issues, run the [ibmcloud cr exemption-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_exemption_list) command.
* To list the types of security issues that you can exempt, run the [ibmcloud cr exemption-types](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_exemption_types) command.
* To delete an exemption for a security issue, run the [ibmcloud cr exemption-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_exemption_rm) command.



For more information about the commands, you can use the --help option when you run the command.
For issues that are created on Git Repos and Issue Tracking, the due date is set in the GitLab native due date field instead of the issue description.

The issue description contains the timestamp when the issue was first discovered. For example, First found on 2022-04-07. The date is in YYYY-MM-DD format. The locations where the problem occurs are listed in the comments of the issue.









 Postponing the due date of an incident issue 

If you want to postpone the due date of an incident issue, you can ask for a review from a security focal. Depending on the review, you can postpone the due date by modifying the Due date field in the Git Repos and Issue Tracking incident issues meta fields.

Zoom

![Setting and updating due date on Git Repos and Issue Tracking](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-native-due-date.png)

Figure 2. Setting and updating due date on Git Repos and Issue Tracking

Be sure to reference the security-focal review in the issue, such as providing a link to it in a comment.



 Postponing the due date of an issue that has a PCE 

If you have an issue that has a Public Cloud Security Exception (PCE), you can change its due date to be the same as the expiration date of the PCE so that evidence collection continues up to the PCE expiration date.







 Slack alerts for pending and overdue issues for CC pipeline 

The Continuous Compliance (CC) pipeline can set due dates for the incident issues. The pipeline can also notify users about issues that have approaching due dates and overdue due dates by using Slack, if Slack integration is enabled.
Release notes 

Use the release notes to learn about the current changes to the IBM Cloud® Schematics documentation that are grouped by month.

IBM Cloud Schematics Agent beta-1 delivers a simplified agent installation process and policy for agent assignment. You can review the [beta-1 release](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-relnotes&interface=clischematics-mar2223) documentation and explore.



 May 2023 

Review the release notes for May 2023.



 22 May 2023 

Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.12.10](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.







 April 2023 

Review the release notes for April 2023.



 18 April 2023 

Schematics documentation realigns the workspace documentation
: The Schematics documentation realigns and upgrades the workspace documentation pages such as [Schematics Workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-create-wks), and [Managing Schematics resources](https://cloud.ibm.com/docs/schematics?topic=schematics-multi-region-deployment).





 13 April 2023 

Schematics updates the deprecation of Terraform versions
: The Schematics announces the timeline for the [deprecation of Terraform versions](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-versiondeprecate-timeline).





 6 April 2023 

Release Schematics command-line plug-in
: The Schematics [command-line plug-in v1.12.9](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) released.







 March 2023 

Review the release notes for March 2023.



 30 March 2023
[Delete action](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/deleteaction.png) When the user selects to delete an existing action, initially action goes into Pending state. If the template deletion fails action goes to Critical state. 
 Update ![Update action](https://cloud.ibm.com/docs-content/v1/content/ba89e173287b28d1453d2a327d8a1f74ae2f1662/schematics/images/updateaction.png) When the user clicks an existing action to update the template repository, immediately action goes to pending state. If the template processing is success, action goes to the Normal state. If the user tries to set the template repository to disable, action goes to the Disabled state. Finally, if the template processing fails, action goes to Critical state. 









 Reviewing Actions job details 

Use the Schematics Actions job details to find a history of all Schematics internal activities. Activities such as downloading your Ansible playbook or verifying your playbook, and to see the Ansible logs for the playbook that you ran on your target hosts.

Jobs are classified into the following categories:



* System jobs: These jobs represent all Schematics internal activities and checks, for example, downloading your Ansible playbook from GitHub or verifying your playbook. You can find these jobs in the All tab on the action's Jobs page.
* User jobs: These jobs are created when you check or run an action. You can find a summary of all user-initiated jobs when you click the User tab on the action's Jobs page.



Review the following status that can be assigned to a job:



Job status

 Status Description 

 ok The total number of target hosts where the Ansible playbook ran. 
 changed The total number of target hosts that were accessed and changed. 
 failed The total number of target hosts where the Ansible playbook might not be successfully ran.
<time>.minusSeconds(_n_) Returns the time n seconds before the specified time. 
 <time>.plusHours(_n_) Returns the time n hours after the specified time. 
 <time>.plusMinutes(_n_) Returns the time n minutes after the specified time. 
 <time>.plusSeconds(_n_) Returns the time n secons after the specified time. 



where <time> is specified in the format HH:mm:ss.

For example, to get the time one hour from now, specify the following expression:

now().plusHours(1)





 Working with time spans 

To show a response based on whether today's date falls within a certain time span, you can use a combination of time-related methods. For example, if you run a special offer during the holiday season every year, you might want to check whether today's date falls between November 25 and December 24 of this year.

First, define the dates of interest as session variables. In the following start and end date session variable expressions, the date is being constructed by concatenating the dynamically-derived current year value with hard-coded month and day values:

start_date = now().reformatDateTime('Y') + '-12-24'
end_date = now().reformatDateTime('Y') + '-11-25'

Then, in a step condition, you can indicate that you want to show the response only if the current date falls between the start and end dates that you defined as session variables:

now().after(${start_date}) && now().before(${end_date})





 java.util.Date support 

In addition to the built-in methods, you can use standard methods of the java.util.Date class.

For example, to get the date of the day that falls a week from today, you can use the following syntax:

new Date(new Date().getTime() + (7 * (2460601000L)))
* [22 May 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-may2220)



* New tutorial for calling an action from another action.



* [15 May 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-may1520)



* New High availability topic.
* Updates for supported runtimes.





* [April 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-apr20)



* [24 April 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-apr2420)



* New Functions CLI version 1.0.39.
* New actions overview topic.
* Improved access policy information.





* [March 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-mar20)



* [24 March 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-mar2420)



* Node.js 8 is deprecated.



* [9 March 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-mar920)



* New Functions CLI version 1.0.38.
* Updated trigger parameters for CLI.
* Updated troubleshooting information for Node.js.
End-of-Marketing 30 November 2022 All IBM Cloud® users, other than those who have an IBM Cloud Foundry application deployed, will be blocked from new application deployments. As of 30 November 2022, new Cloud Foundry Organizations (Orgs) cannot be created by any user. 
 Reminders Ongoing Periodic reminders will be sent to all users with running IBM Cloud Foundry applications that the end-of-support date is coming, with increasing frequency as the date approaches. 
 End-of-Support 1 June 2023 Running IBM Cloud Foundry applications will be permanently disabled and deprovisioned by the IBM Cloud Foundry team. 







 IBM Cloud Foundry deprecation details 

Some details of this announcement:



* A "deprecation" is a process, and we've announced the beginning of that process. It begins with the "Announcement" (this page), continues with "End-of-Marketing", and ends with "End-of-Support". Nothing happens until those announced dates above.
* At the "End-of-Marketing", users that don't have IBM Cloud Foundry running workloads will be blocked from deploying new applications. All users that have Cloud Foundry application instances deployed can still keep deploying and re-deploying applications normally and as needed. Also at this time, new Cloud Foundry Organizations (Orgs) cannot be created by any user.
* At the "End-of-Support", all IBM Cloud Foundry applications will, in a short period of time, be stopped and the deployed runtime applications deleted.
* All other services you have been using in IBM Cloud, possibly from your IBM Cloud Foundry applications, are unaffected - the IBM Cloud Foundry deprecation refers only to the specific IBM Cloud Foundry application runtime instances you have running, not services you might use with your IBM Cloud Foundry applications.
* Runtimes available on IBM Cloud Foundry, for example, Node, Liberty, Java, and so on, will still be available on other compute services.
* If you move to another IBM Cloud compute service, you should be able to connect to those previous connected services and continue using them normally.
* All IBM Cloud Foundry application instances running on IBM Cloud®, and all services and components that use IBM Cloud Foundry capabilities, will remain fully functional until the End-of-Support date.
Return only managed keys whose activation date matches the parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--activation-date-min (string)
: Optional. Return only managed keys whose activation date is at or after the parameter value. This query parameter cannot be used in conjunction with the activation_date query parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--activation-date-max (string)
: Optional. Return only managed keys whose activation date is at or before the parameter value. This query parameter cannot be used in conjunction with the activation_date query parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--deactivation-date (string)
: Optional. Return only managed keys whose deactivation date matches the parameter. This query parameter cannot be used in conjunction with the expiration_date query parameter. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--deactivation-date-min (string)
: Optional. Return only managed keys whose deactivation date is at or after the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, expiration_date_min, and expiration_date_max query parameters. The value must match regular expression /[0-9]{4}-[0-9]{2}-[0-9]{2}/.

--deactivation-date-max (string)
: Optional. Return only managed keys whose deactivation date is at or before the parameter value. This query parameter cannot be used in conjunction with the deactivation_date, expiration_date, expiration_date_min, and expiration_date_max query parameters.
[uniqueId] => 750352919747xxx
[vendorName] => akamai
)

Show more

Calls to stopDomainMapping and startDomainMapping will return the same Mapping object, with the status being the difference.

[0] => SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping Object
(
...

[status] => STOPPED
[uniqueId] => 750352919747xxx

...
)

[0] => SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping Object
(
...

[status] => RUNNING
[uniqueId] => 750352919747xxx

...
)