Build 2047

Author: cfsdocs

cli-changelog.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-12"
+lastupdated: "2024-01-25"
 
 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.49.3 | 2024-01-25 | - Fixed various bugs. |
 | 1.49.2 | 2024-01-12 | - Fixed various bugs. |
 | 1.49.1 | 2023-12-06 | - Fixed various bugs. |
 | 1.49.0 | 2023-12-01 | - Added the `--array-size-variable-override` option the **`jobrun submit`** and **`jobrun resubmit`** commands. Use this option to specify a custom value for the `JOB_ARRAY_SIZE` environment variable. See [Processing a subset of data by dynamically assigning work to parallel job run instances](/docs/codeengine?topic=codeengine-job-run-parallel#job-run-parallel-dynamic). \n - Renamed the `--instances` option to `--array-size` for the **`job create`**, **`job update`**, **`jobrun submit`**, and **`jobrun resubmit`** commands. Note that `--instances` is still valid as an alias for `--array-size`. \n - Fixed various bugs. |

fun-create-existing.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2023, 2024
-lastupdated: "2024-01-09"
+lastupdated: "2024-01-25"
 
 keywords: functions in code engine, functions, serverless, create functions in code engine, function workloads in code engine, registry secret, registry access, registry access secret
 
@@ -125,7 +125,7 @@ To access an existing code bundle from a private registry, you must set up acces
 3. Create your function and reference a code bundle in a private registry in {{site.data.keyword.registryshort}}. For example, use the [**`ibmcloud ce fn create`**](/docs/codeengine?topic=codeengine-cli#cli-function-create) command to create the `myhellofun` function to reference the `icr.io/codeengine/samples/function-nodejs-codebundle` by using the `myregistry` access information. 
 
     ```txt
-    ibmcloud ce fn create --name myhellofun --image icr.io/NAMESPACE/REGISTRY:TAG --registry-secret myregistry
+    ibmcloud ce fn create --name myhellofun --code-bundle icr.io/NAMESPACE/REGISTRY:TAG --registry-secret myregistry
     ```
     {: pre}
 

logging.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-24"
+lastupdated: "2024-01-25"
 
 keywords: logging for code engine, logs for code engine, job logs for code engine, app logs for code engine, build logs for code engine, logs
 
@@ -79,7 +79,7 @@ After you select the project that you want to work with, you can add logging cap
 2. From your {{site.data.keyword.codeengineshort}} app page, you can add logging capabilities. If you have previously created a {{site.data.keyword.la_short}} instance, click **Logging**, and this action opens the {{site.data.keyword.la_short}} service. Else, complete the following steps to configure logging capabilities.
     1. From the **Test application** options menu, click **Add logging** to create the {{site.data.keyword.la_full_notm}} instance. This action opens the {{site.data.keyword.la_short}} service.  
     2. From the {{site.data.keyword.la_short}} service, create your logging instance. To confirm that your logging instance is created, check the [Observability dashboard](https://cloud.ibm.com/observe/logging). 
-    3. From your {{site.data.keyword.codeengineshort}} app page, click **Add logging** from the **Test application** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you. **CHECK - CORRECT???**
+    3. From your {{site.data.keyword.codeengineshort}} app page, click **Add logging** from the **Test application** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you. 
 3. Now that platform logs are configured, from your {{site.data.keyword.codeengineshort}} app page, click **Logging** from the **Test application** options menu to open your platform logs window. Be sure to keep this platform logs window open to receive your logging data if you are using the {{site.data.keyword.la_short}} free tier. You don't need to keep this window open if you are using a {{site.data.keyword.la_short}} paid tier as log data is preserved for a configurable amount of time, depending on your plan. To confirm that platform logs are set for your region, check the [Observability dashboard](https://cloud.ibm.com/observe/logging). 
 4. (optional) Refine the [filter for your search](#view-logs-filters), if needed. 
 5. Test your 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**. You can view platform logs from the test of your application in the platform logs window. 
@@ -98,7 +98,7 @@ After you select the project that you want to work with, you can add logging cap
 2. From your {{site.data.keyword.codeengineshort}} job page, you can add logging capabilities. If you have previously created a {{site.data.keyword.la_short}} instance, click **Logging**, and this action opens the {{site.data.keyword.la_short}} service. Else, complete the following steps to configure logging capabilities.
     1. From the **Submit job** options menu, click **Add logging** to create the {{site.data.keyword.la_full_notm}} instance. This action opens the {{site.data.keyword.la_short}} service.  
     2. From the {{site.data.keyword.la_short}} service, create your logging instance. To confirm that your logging instance is created, check the [Observability dashboard](https://cloud.ibm.com/observe/logging). 
-    3. From your {{site.data.keyword.codeengineshort}} job page, click **Add logging** from the **Submit job** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you. **CHECK - CORRECT???**
+    3. From your {{site.data.keyword.codeengineshort}} job page, click **Add logging** from the **Submit job** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you. 
 3. Now that platform logging is configured, from your {{site.data.keyword.codeengineshort}} job page, click **Logging** from the **Submit job** options menu to open your platform logs window. Be sure to keep this platform logs window open to receive your logging data if you are using the {{site.data.keyword.la_short}} free tier. Don't keep this window open if you are using a {{site.data.keyword.la_short}} paid tier.  
 4. (optional) Refine the [filter for your search](#view-logs-filters), if needed. 
 5. Run your job. From the **Job runs** area, click **Submit job** to run your job. Provide the job run configuration values or you can take the default values. Click **Submit job** to run your job. You can view platform logs from the job run in the platform logs window. 
@@ -117,7 +117,7 @@ After you select the project that you want to work with, you can add logging cap
 2. From your {{site.data.keyword.codeengineshort}} function page, you can add logging capabilities. If you have previously created a {{site.data.keyword.la_short}} instance, click **Logging**, and this action opens the {{site.data.keyword.la_short}} service. Else, complete the following steps to configure logging capabilities.
     1. From the **Test function** options menu, click **Add logging** to create the {{site.data.keyword.la_full_notm}} instance. This action opens the {{site.data.keyword.la_short}} service.  
     2. From the {{site.data.keyword.la_short}} service, create your logging instance. To confirm that your logging instance is created, check the [Observability dashboard](https://cloud.ibm.com/observe/logging). 
-    3. From your {{site.data.keyword.codeengineshort}} function page, click **Add logging** from the **Test function** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you. **CHECK - CORRECT???**
+    3. From your {{site.data.keyword.codeengineshort}} function page, click **Add logging** from the **Test function** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you. 
 3. Now that platform logging is configured, from your {{site.data.keyword.codeengineshort}} function page, click **Logging** from the **Test function** options menu to open your platform logs window. Be sure to keep this platform logs window open to receive your logging data if you are using the {{site.data.keyword.la_short}} free tier. You don't need to keep this window open if you are using a {{site.data.keyword.la_short}} paid tier as log data is preserved for a configurable amount of time, depending on your plan. To confirm that platform logs are set for your region, check the [Observability dashboard](https://cloud.ibm.com/observe/logging). 
 4. (optional) Refine the [filter for your search](#view-logs-filters), if needed. 
 5. Test your function. Click **Test function**, and then click **Send request** in the Test function pane. To open the function in a web page, click **Function URL**. You can view platform logs from the test of your function in the platform logs window. 

release-notes.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-22"
+lastupdated: "2024-01-25"
 
 keywords: release notes for code engine, updates in code engine, what's new in code engine, document changes in code engine, updates, release notes
 
@@ -26,6 +26,14 @@ Use the release notes to learn about the latest changes to {{site.data.keyword.c
 Review the release notes for January 2024.  
 {: shortdesc}
 
+### 25 January 2024
+{: #codeengine-jan2524}
+{: release-note}
+
+[CLI release]{: tag-purple} CLI version 1.49.3 released
+:   See [CLI version history](/docs/codeengine?topic=codeengine-cli_versions).
+
+
 ### 22 January 2024
 {: #codeengine-jan2224}
 {: release-note}

sitemap.md

@@ -2,7 +2,7 @@
 
 copyright:
   years: 2024
-lastupdated: "2024-01-24"
+lastupdated: "2024-01-25"
 
 keywords: sitemap, code engine, about, tutorial, project, app, job, configmaps, secret, event, log, monitor, cli, api, troubleshoot, support, source code, faq, memory, cpu, commands, arguments, release notes
 
@@ -140,6 +140,10 @@ Find what you are looking for in the compilation of {{site.data.keyword.codeengi
 
     * Review the release notes for January 2024.  
 
+    * [25 January 2024](/docs/codeengine?topic=codeengine-codeengine-relnotes#codeengine-jan2524)
+
+        * [CLI release]{: tag-purple} CLI version 1.49.3 released
+
     * [22 January 2024](/docs/codeengine?topic=codeengine-codeengine-relnotes#codeengine-jan2224)
 
         * [Update]{: tag-magenta} Updated the user experience for making configuration changes to apps in the console