Merge pull request #471 from cloud-docs/next-publish-push

Next publish push

Author: Kersten Richter

appdeploy-private.md

@@ -42,7 +42,7 @@ Before you can work with a {{site.data.keyword.codeengineshort}} application tha
 8. For **Registry access secret**, select **Create registry access secret**. 
 9. From the Create registry access secret page, choose your registry source. For example, **Docker Hub**.
 10. Enter a username. For Docker Hub, it is your Docker ID.
-11. Enter the password. For Docker Hub, you can use your Docker Hub password or an access token. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/docker-hub/access-tokens/){: external}.
+11. Enter the password. For Docker Hub, you can use your Docker Hub password or an access token. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/security/for-developers/access-tokens/){: external}.
 12. Click **Create** to add a registry access secret for {{site.data.keyword.codeengineshort}}.
 13. From the Configure image page, the registry access secret that was added is listed. Select the registry access secret for your image.
 14. Select the namespace and name of the image in Docker Hub for the {{site.data.keyword.codeengineshort}} app to reference. For example, select `mynamespace` and select the image `hello_repo` in that namespace.
@@ -71,7 +71,7 @@ Before you begin
 
 Before you can work with a {{site.data.keyword.codeengineshort}} application that references an image in a private registry, you must first add access to the registry, pull the image, and then deploy it. 
 
-1. To pull images from a private registry, you must first create a private registry. For example, to create a private Docker Hub registry, see [Docker Hub documentation](https://docs.docker.com/docker-hub/repos/){: external}. After you create a private registry, [push an image to it](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub){: external}. You can also set up an access token. By using an access token, you can more easily grant and revoke access to your Docker Hub account without requiring a password change. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/docker-hub/access-tokens/){: external}.
+1. To pull images from a private registry, you must first create a private registry. For example, to create a private Docker Hub registry, see [Docker Hub documentation](https://docs.docker.com/docker-hub/repos/){: external}. After you create a private registry, [push an image to it](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub){: external}. You can also set up an access token. By using an access token, you can more easily grant and revoke access to your Docker Hub account without requiring a password change. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/security/for-developers/access-tokens/){: external}.
 
 2. Add access to your private registry to pull images. To add access to a private registry with the CLI, use the [**`ibmcloud ce secret create --format registry`**](/docs/codeengine?topic=codeengine-cli#cli-secret-create) command to create a registry secret. For example, the following command creates registry access to a Docker Hub registry called `privatedocker` that is at `'https://index.docker.io/v1/'` and uses your username and password.
 

job-create-private.md

@@ -42,7 +42,7 @@ Before you can work with a {{site.data.keyword.codeengineshort}} job that refere
 8. For **Registry access secret**, select **Create registry access secret**.
 9. From the Create registry access secret page, choose your registry source. For example, **Docker Hub**.
 10. From the Create registry access secret page, enter a username. For Docker Hub, it is your Docker ID.
-11. From the Create registry access secret page, enter the password. For Docker Hub, you can use your Docker Hub password or an access token. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/docker-hub/access-tokens/){: external}.
+11. From the Create registry access secret page, enter the password. For Docker Hub, you can use your Docker Hub password or an access token. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/security/for-developers/access-tokens/){: external}.
 12. Click **Create** to add the registry access for {{site.data.keyword.codeengineshort}}.
 13. From the Configure image page, the registry access secret that was added is listed. Select the registry access secret for your image.
 14. Select the namespace and name of the image in Docker Hub for the {{site.data.keyword.codeengineshort}} job to reference. For example, select `mynamespace` and select the image `testjob` in that namespace.
@@ -66,7 +66,7 @@ Before you begin
 * [Create and work with a project](/docs/codeengine?topic=codeengine-manage-project).
 * Before you can work with a {{site.data.keyword.codeengineshort}} job that references an image in a private registry, you must first add access to the registry, pull the image, and then create your job configuration.
 
-1. To pull images from a private registry, you must first create a private registry. For example, to create a private Docker Hub registry, see [Docker Hub documentation](https://docs.docker.com/docker-hub/repos/){: external}. After you create a private registry, [push an image to it](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub){: external}. You can also set up an access token. By using an access token, you can more easily grant and revoke access to your Docker Hub account without requiring a password change. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/docker-hub/access-tokens/){: external}.
+1. To pull images from a private registry, you must first create a private registry. For example, to create a private Docker Hub registry, see [Docker Hub documentation](https://docs.docker.com/docker-hub/repos/){: external}. After you create a private registry, [push an image to it](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub){: external}. You can also set up an access token. By using an access token, you can more easily grant and revoke access to your Docker Hub account without requiring a password change. For more information about access tokens and Docker Hub, see [Managing access tokens](https://docs.docker.com/security/for-developers/access-tokens/){: external}.
 
 2. Add access to your private registry to pull images. To add access to a private registry with the CLI, use the [**`ibmcloud ce secret create --format registry`**](/docs/codeengine?topic=codeengine-cli#cli-secret-create) command to create an registry secret. For example, the following command creates registry access to a Docker Hub registry called `privatedocker` that is at ``https://index.docker.io/v1/`` and uses your username and password.
 

job-run-parallel.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2020, 2023
-lastupdated: "2023-11-30"
+  years: 2023, 2023
+lastupdated: "2023-12-12"
 
 keywords: jobs in code engine, batch jobs in code engine, running jobs with code engine, creating jobs with code engine, images for jobs in code engine, jobs, parallel jobs, parallel batch jobs
 subcollection: codeengine
@@ -65,7 +65,7 @@ However, suppose you want to rerun 3 of the initial 10 job run instances because
 
 For this new job run, say that you update only the array indices; for example, `"3, 7, 9"`. Because the value of the `JOB_ARRAY_SIZE` environment variable is automatically computed when array indices are specified instead of the array size, the value of `JOB_ARRAY_SIZE` is now 3 instead of 10, since 3 array indices were specified.
 
-Instead, to ensure that your jobrun submit (or resubmit) processes the correct chunks of data for the specified indices `3`, `7`, and `9`, you can override the automatically computed value of `JOB_ARRAY_SIZE` by using the `--array-size-var-override` option in the CLI or by specifying a custom value for `JOB_ARRAY_SIZE` in the console. 
+Instead, to ensure that your jobrun submit (or resubmit) processes the correct chunks of data for the specified indices `3`, `7`, and `9`, you can override the automatically computed value of the `JOB_ARRAY_SIZE` environment variable by using the `--array-size-var-override` option in the CLI or by specifying a custom value in the `JOB_ARRAY_SIZE` input field in the console.
 
 By setting the custom array size override value to 10, the job run instances correctly compute the chunk size as 10% and the resubmitted job run instances process the desired data (indices `3`, `7`, and `9`). You can use this option to enforce a constant array size value for job rerun scenarios, where only some job instances are submitted or resubmitted.
 

lithops.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2022
-lastupdated: "2022-11-21"
+  years: 2023
+lastupdated: "2023-12-12"
 
 keywords: lithops and code engine, lithops framework and code engine, Python and code engine, iam api key when using lithops for code engine, jobs in lithops framework with code engine, batch jobs in lithops framework with code engine, lithops, jobs
 
@@ -49,7 +49,7 @@ Select a [supported storage backend](https://github.com/lithops-cloud/lithops/tr
 
 To set up {{site.data.keyword.cos_full_notm}}, 
 
-1. Create an [{{site.data.keyword.cos_full_notm}} account](https://www.ibm.com/cloud/object-storage).
+1. Create an [{{site.data.keyword.cos_full_notm}} account](https://www.ibm.com/products/cloud-object-storage).
 2. Create a bucket in the region that you want to use.
 3. In the side navigation, click **Endpoints** to find your API endpoint. You must copy both the public and private endpoints of the region where you created your bucket.
 4. Create the credentials to access to your {{site.data.keyword.cos_full_notm}} account. **Choose one option**