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

foverby · GitHub Enterprise · commit 9cd0a8509e08 · 2024-01-25T12:17:46.000-05:00
Next publish push
diff --git a/batch-tutorial.md b/batch-tutorial.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2024
-lastupdated: "2024-01-17"
+lastupdated: "2024-01-25"
 
 keywords: job tutorial, jobs, images for code engine jobs, tutorial for code engine, job log
 
@@ -103,7 +103,7 @@ When the job is in a ready state, you can update the job. Let's update the job t
 4. From the Submit job pane, review and optionally change default configuration values such as instances, CPU, memory, number of job retries, and job timeout. You can specify either **Array size** or **Array indices** for the parallel job instances to run. For **Array size**, provide the number of instances to run in parallel for this job. For **Array indices**, provide a comma-separated list for your custom set of indices. For example, to run this job with a custom set of `5` indices, specify `3,12-14,25`. Click **Submit job** again to run your job. The system displays the status of the instances of your job on the Job details page. 
 5. By [viewing job logs from the console](/docs/codeengine?topic=codeengine-view-logs#view-joblogs-ui) for this job, the output of the job is `Hello World!`.
 6. To update the job again and add an environment variable, navigate to your job page. 
-7. From the **Configuration > Enviroment variables** tab, click **Add environment variable**. Add a literal environment variable with the name of `TARGET` with a value of `Sunshine`. The `icr.io/codeengine/testjob` outputs the message, `Hello <value_of_TARGET>!>`.
+7. From the **Configuration > Environment variables** tab, click **Add environment variable**. Add a literal environment variable with the name of `TARGET` with a value of `Sunshine`. The `icr.io/codeengine/testjob` outputs the message, `Hello <value_of_TARGET>!>`.
 8. Click **Add** to add your environment variable and then click **Save** to save the changes to your job. 
 9. Click **Submit job** to submit the updated job.
 10. From the Submit job pane, review and optionally change default configuration values such as instances, CPU, memory, number of job retries, and job timeout. This time, specify **Array size** as `3`. Click **Submit job** again to run your job. The system displays the status of the instances of your job on the Job details page. From the `Configuration` section of the Job details page, the information about the number of instances is displayed as **Array indices**, which is `0 - 2` for this example. 
diff --git a/billing.md b/billing.md
@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2023
-lastupdated: "2023-11-08"
+  years: 2024
+lastupdated: "2024-01-23"
 
 keywords: billing, pricing, costs for code engine, billing for code engine, job pricing, app pricing, build pricing
 
@@ -59,6 +59,8 @@ For valid CPU and memory combinations, see [Supported memory and CPU combination
 
 Note that the time that it takes to pull your image or to build it from source code is included in the billable time.
 
+
+
 ## Build pricing
 {: #build-pricing}
 
diff --git a/cli-changelog.md b/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. |
diff --git a/cmd_defs.md b/cmd_defs.md
@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2023
-lastupdated: "2023-11-30"
+  years: 2024
+lastupdated: "2024-01-23"
 
 keywords: cli for code engine, command-line interface for code engine, cli commands for code engine, reference for code engine cli, ibmcloud ce, ibmcloud codeengine, commands, code engine cli, apps, jobs, source code, configmap, build repository, build, secret, image repository, registry, example, example output
 
@@ -61,7 +61,7 @@ ibmcloud ce application bind --name APP_NAME (--service-instance SI_NAME | --ser
  {: #cmd-options-application-bind} 
 
 `--name`, `-n`
-:   The name of the application to bind. This value is *required*. 
+:   The name of the application to bind. This value is *required*.  
 
 `--no-wait`, `--nw`
 :   Bind the service instance and do not wait for the service binding to be ready. If you specify the `no-wait` option, the service binding creation is started and the command exits without waiting for it to complete. Use the `app get` command to check the application bind status. This value is *optional*. The default value is `false`.
diff --git a/fun-create-existing.md b/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}
 
diff --git a/landing.json b/landing.json
@@ -1,6 +1,6 @@
 {
     "title": "Code Engine",
-    "lastupdated": "2024-01-22",
+    "lastupdated": "2024-01-25",
     "introduction": "Find out how you can use Code Engine to run your containerized workloads",
     "section_devtools": {
       "api": "/apidocs/codeengine/v2", 
diff --git a/logging.md b/logging.md
diff --git a/release-notes.md b/release-notes.md
diff --git a/sitemap.md b/sitemap.md

Original file line number	Diff line number	Diff line change
`@@ -1,6 +1,6 @@`
`1`	`1`	`{`
`2`	`2`	`"title": "Code Engine",`
`3`		`- "lastupdated": "2024-01-22",`
	`3`	`+ "lastupdated": "2024-01-25",`
`4`	`4`	`"introduction": "Find out how you can use Code Engine to run your containerized workloads",`
`5`	`5`	`"section_devtools": {`
`6`	`6`	`"api": "/apidocs/codeengine/v2",`