Merge pull request #179 from cloud-docs/next-prod-push

Next publish push

Author: foverby

app-tutorial.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-12"
+lastupdated: "2022-01-13"
 
 keywords: app tutorial for code engine, application, apps, images, tutorial for code engine, deploying
 
@@ -37,7 +37,7 @@ Tutorials might incur costs. Use the Cost Estimator to generate a cost estimate
 {: #deploy-app-image-file}
 {: step}
 
-This tutorial uses a sample image, `icr.io/codeengine/hello`, which is a simple `Hello World` program. The program includes an environment variable `TARGET`, and prints `Hello ${TARGET}`. If the environment variable is empty, `Hello World` is returned. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/blob/main/hello){: external}.
+This tutorial uses a sample image, `icr.io/codeengine/hello`, which is a simple `Hello World` program. The program includes an environment variable `TARGET`, and prints `Hello ${TARGET}`. If the environment variable is empty, `Hello World` is returned. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/tree/main/hello){: external}.
 
 If you have a container image that you want to use, you can replace the image reference in the next step with your own Docker repository, image name, and version.
 

appdeploy-update.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-12"
+lastupdated: "2022-01-13"
 
 keywords: applications in code engine, apps in code engine, http requests in code engine, deploy apps in code engine, app workloads in code engine, deploying workloads in code engine, application, app, memory, cpu, environment variables
 
@@ -86,7 +86,7 @@ To update your app with the CLI, use the **`app update`** command. This command
 
 Update the application that you created in [Deploying an application with the CLI](/docs/codeengine?topic=codeengine-deploy-app#deploy-app-cli) to add an environment variable. 
 
-The sample `icr.io/codeengine/hello` image reads the environment variable `TARGET`, and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. The following example updates the app to modify the value of the `TARGET` environment variable to `Stranger`. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/blob/main/hello){: external}.
+The sample `icr.io/codeengine/hello` image reads the environment variable `TARGET`, and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. The following example updates the app to modify the value of the `TARGET` environment variable to `Stranger`. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/tree/main/hello){: external}.
 
 1. Run the **`application update`** command. For example,
 

cli-changelog.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-06"
+lastupdated: "2022-01-13"
 
 keywords: cli change log for code engine, cli version for code engine, change log for cli in code engine, cli history for code engine, change log, cli version history
 
@@ -20,6 +20,7 @@ Find a summary of changes for each version of {{site.data.keyword.codeenginefull
 
 | Version | Release date | Changes |
 | ----- | ------- | -------------- |
+| 1.24.0 | 13 January 2022| - Added the **`application restart`** and **`jobrun restart`** commands to restart running app and job run instances. \n - Added the **`buildrun cancel`** command to stop a running build run.  \n -  Added support for working with configuration maps and secrets with jobs and job runs as mounted files. For this support, added the `--mount-configmap` and `--mount-secret` options to the **`job create`**, **`job update`**, **`jobrun submit`** and **`jobrun resubmit`** commands. Added the `--mount-rm` option to the **`job update`** and **`jobrun resubmit`** commands to remove the contents of the configmap or secret from the file system for the job or job run. Updated the output for the **`job get`** and **`jobrun get`** commands to add a `Mounts` section to display information about mounted files.  \n - Updated description of `kubecfg` option for the **`project select`** command to clarify that the `KUBECONFIG` environment variable can be used to override the Kubernetes configuration file. \n - Fixed various bugs. \n - Updated translations for the CLI. \n - Upgraded to Go 1.17.6.|
 | 1.23.3 | 15 December 2021 | - Fixed various bugs.  \n - Updated translations for the CLI. \n - Upgraded to Go 1.17.5. |
 | 1.23.2 | 01 December 2021 | - Fixed various bugs.  \n - Updated translations for the CLI. |
 | 1.23.1 | 19 November 2021 | - Fixed various bugs. |

cmd_defs.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2022
-lastupdated: "2022-01-12"
+lastupdated: "2022-01-13"
 
 keywords: configmaps with code engine, secrets with code engine, key references with code engine, key-value pair with code engine, referencing secrets with code engine, referencing configmaps with code engine, configmaps, secrets, environment variables
 
@@ -15,7 +15,7 @@ subcollection: codeengine
 # Referencing secrets and configmaps as mounted files (CLI)
 {: #secretcm-reference-mountedfiles}
 
-In {{site.data.keyword.codeengineshort}}, after you create secrets and configmaps, the information that is stored as key-value pairs can be consumed by your application as a mounted file. 
+In {{site.data.keyword.codeengineshort}}, after you create secrets and configmaps, the information that is stored as key-value pairs can be consumed by your job or application as a mounted file. 
 {: shortdesc}
 
 Working with secrets and configmaps as mounted files is similar to working with secrets and configmaps as environment variables. 

configmap-secret-referencing-vol.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-12"
+lastupdated: "2022-01-13"
 
 keywords: configmaps with code engine, secrets with code engine, key references with code engine, key-value pair with code engine, setting up secrets with code engine, setting up configmaps with code engine, configmaps, secrets, environment variables
 
@@ -256,7 +256,7 @@ The following example describes how to reference an existing configmap with an a
     ```
     {: pre}     
 
-2. [Deploy an app](/docs/codeengine?topic=codeengine-deploy-app#deploy-app-cli) and reference the `myliteralconfigmap` configmap. For this example, create an app that uses the `hello` image. When a request is sent to this sample app, the app reads the environment variable `TARGET` and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. Reference the `myliteralconfigmap` configmap. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/blob/main/hello){: external}.
+2. [Deploy an app](/docs/codeengine?topic=codeengine-deploy-app#deploy-app-cli) and reference the `myliteralconfigmap` configmap. For this example, create an app that uses the `hello` image. When a request is sent to this sample app, the app reads the environment variable `TARGET` and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. Reference the `myliteralconfigmap` configmap. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/tree/main/hello){: external}.
 
     ```sh
     ibmcloud ce app create --name myhelloapp --image icr.io/codeengine/hello --env-from-configmap myliteralconfigmap
@@ -365,7 +365,7 @@ When you use the `--force` option with these commands, the action to create, upd
 
 The following example describes how to reference a configmap that is not yet defined with an app by using the CLI. 
 
-1. [Create an app](/docs/codeengine?topic=codeengine-application-workloads) and reference the undefined `myliteralconfigmap3` configmap. For this example, create a {{site.data.keyword.codeengineshort}} app that uses the `icr.io/codeengine/hello` image. When a request is sent to this sample app, the app reads the environment variable `TARGET` and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. Reference the `myliteralconfigmap3` configmap. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/blob/main/hello){: external}.
+1. [Create an app](/docs/codeengine?topic=codeengine-application-workloads) and reference the undefined `myliteralconfigmap3` configmap. For this example, create a {{site.data.keyword.codeengineshort}} app that uses the `icr.io/codeengine/hello` image. When a request is sent to this sample app, the app reads the environment variable `TARGET` and prints `Hello ${TARGET}`. If this environment variable is empty, `Hello World` is returned. Reference the `myliteralconfigmap3` configmap. For more information about the code that is used for this example, see [`hello`](https://github.com/IBM/CodeEngine/tree/main/hello){: external}.
 
     By using the `--no-wait` option with the **`app create`** command, the app is created and does not wait for the app to be ready. 
 

configmap-secret.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-12"
+lastupdated: "2022-01-13"
 
 keywords: getting started with ibm cloud code engine, code engine, ibm cloud code engine, jobs in code engine, apps in code engine, builds with code engine, {{site.data.keyword.codeenginefull_notm}}, building container image, source code
 
@@ -56,7 +56,7 @@ Create your first {{site.data.keyword.codeengineshort}} app by using the `icr.io
 3. Select **Application**.
 4. Enter a name for the application. Use a name for your application that is unique within the project. 
 5. Select a project from the list of available projects. You can also [create a new one](/docs/codeengine?topic=codeengine-manage-project#create-a-project). Note that you must have a selected project to deploy an app.
-6. Select to run a **Container image** and specify `icr.io/codeengine/helloworld` for the image reference. For this example, you do not need to modify the default values for endpoint or runtime settings. For more information about the code that is used for this example, see [`helloworld`](https://github.com/IBM/CodeEngine/blob/main/helloworld){: external}.
+6. Select to run a **Container image** and specify `icr.io/codeengine/helloworld` for the image reference. For this example, you do not need to modify the default values for endpoint or runtime settings. For more information about the code that is used for this example, see [`helloworld`](https://github.com/IBM/CodeEngine/tree/main/helloworld){: external}.
 7. Click **Create**. 
 8. After the application status changes to **Ready**, you can test the application. Click **Test application** and then click **Send request** in the Test application pane. To open the application in a web page, click **Application URL**.  
 

getting-started.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2021
-lastupdated: "2021-12-15"
+  years: 2022
+lastupdated: "2022-01-13"
 
 keywords: monitoring for code engine, performance metrics, monitor, metrics, requests, pods, application, attributes, jobrun, panic mode, custom dashboards
 
@@ -35,7 +35,7 @@ Before you can create a custom dashboard in {{site.data.keyword.mon_short}}, you
 
 2. Ensure that there is monitoring data available. Because designing a custom dashboard is easier when you have data to monitor, it is important to have a running [application](/docs/codeengine?topic=codeengine-application-workloads) or [job](/docs/codeengine?topic=codeengine-job-plan). Some of the {{site.data.keyword.codeengineshort}} metrics only exist if they are available in the environment. 
 
-3. Review the available [metrics](/docs/codeengine?topic=codeengine-monitor#metrics-available-by-service-plan) for {{site.data.keyword.codeengineshort}}.
+3. Review the available [metrics](/docs/codeengine?topic=codeengine-monitor#metrics-by-plan) for {{site.data.keyword.codeengineshort}}.
 
 4. Access your {{site.data.keyword.mon_full_notm}} metrics.
     1. From the {{site.data.keyword.cloud_notm}} navigation menu, select **Observability**.

monitor-custom.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2022
-lastupdated: "2022-01-07"
+lastupdated: "2022-01-13"
 
 keywords: build for code engine, planning for code engine, source code building for code engine, source code repositories and code engine, image builds for code engine, container image builds for code engine, build strategy for code engine, build size for code engine, build, build run, source repository, image registry
 
@@ -25,7 +25,7 @@ A build, or image build, is a mechanism that you can use to create a container i
 ## Prepare your source location
 {: #build-plan-repo}
 
-To give {{site.data.keyword.codeengineshort}} access to your source code, you need to make it available in a Git repository
+To give {{site.data.keyword.codeengineshort}} access to your source code, you need to make it available in a Git repository.
 {: shortdesc}
 
 Git repository
@@ -51,13 +51,13 @@ When you pull an image from Docker Hub to use with apps or jobs in Code Engine,
 
 | Runtime   | Version | Samples |
 | --------- | ------- | ------- |
-| Go        | 1.16.9  | [Go samples](https://github.com/paketo-buildpacks/samples/tree/main/go){: external}. |
+| Go        | 1.16.12  | [Go samples](https://github.com/paketo-buildpacks/samples/tree/main/go){: external}. |
 | Java      | 11.0.13  | [Java samples](https://github.com/paketo-buildpacks/samples/tree/main/java){: external}. |
-| Node.js   | 16.13.0 | [Node.js samples](https://github.com/paketo-buildpacks/samples/tree/main/nodejs){: external}. |
+| Node.js   | 16.13.1 | [Node.js samples](https://github.com/paketo-buildpacks/samples/tree/main/nodejs){: external}. |
 | PHP       | 8.0.13  | [PHP samples](https://github.com/paketo-buildpacks/samples/tree/main/php){: external}. |
 | Python    | 3.8.12  | [Python samples](https://github.com/paketo-buildpacks/samples/tree/main/python){: external}. |
-| Ruby      | 2.7.4   | [Ruby samples](https://github.com/paketo-buildpacks/samples/tree/main/ruby){: external}. |
-| .NET Core | 5.0.403 (.NET Core SDK), \n 5.0.12 (.NET Core Runtime) | [.NET Core samples](https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core){: external}. |
+| Ruby      | 2.7.5   | [Ruby samples](https://github.com/paketo-buildpacks/samples/tree/main/ruby){: external}. |
+| .NET Core | 6.0.101 (.NET Core SDK), \n 6.0.1 (.NET Core Runtime) | [.NET Core samples](https://github.com/paketo-buildpacks/samples/tree/main/dotnet-core){: external}. |
 {: caption="Runtime sample files" caption-side="top"}
 
 

plan-build.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-12"
+lastupdated: "2022-01-13"
 
 keywords: release notes for code engine, updates in code engine, what's new in code engine, document changes in code engine, updates, release notes
 
@@ -24,6 +24,16 @@ Use the release notes to learn about the latest changes to {{site.data.keyword.c
 Review the release notes for January 2022.
 {: shortdesc}
 
+### 13 January 2022
+{: #13jan2022}
+{: release-note}
+
+Review the release notes for 13 January 2022.
+{: shortdesc}
+
+CLI version 1.24.0 released.
+:   See [CLI version history](/docs/codeengine?topic=codeengine-cli_versions).
+
 ### 12 January 2022
 {: #12jan2022}
 {: release-note}