Working with the Periodic timer (cron) event producer

Subscribing to Periodic timer (cron) events for an application from the console

You can create and update Periodic timer event subscriptions for an application from the console.

Before you begin

• Create a project.
• Create an application. For example, create an application that is called myapp that uses the icr.io/codeengine/cron image. This image is built from cron.go, available from the Samples for IBM Cloud Code Engine GitHub repo.

Complete the following steps to create and update a Periodic timer event subscription for an application from the console.

1. From the Code Engine Projects page, go to your project.

2. From the Overview page, click Event subscriptions.

3. From the Event subscriptions page, click Create to create your subscription.

4. From the Create event subscription page, complete the following steps:

   1. For Event type, select the Periodic timer tile. Click Next.
   2. For General, provide a name for the Periodic timer subscription, for example, myptimer. You can optionally provide event attributes. Note that if the Periodic timer event consumer is an application, event attributes are available as HTTP headers. If the event consumer is a job, event attributes are available as environment variables. Click Next to proceed.
   3. For Schedule, provide information about the timing of the events. The Periodic timer event producer uses standard crontab syntax to specify interval details. Choose your interval from the provided patterns or provide your own custom cron expression, such as 0 0 * * *, which specifies for the event to occur every day at midnight. For this example, select the schedule pattern for every day, every hour, every minute. Notice that the cron expression is generated for you. The day, hour, and minute patterns and the Cron expression are in Coordinated Universal Time (UTC). If you do not specify a schedule, then this event subscription sends an event every minute. A list of upcoming scheduled events is displayed. Notice that these upcoming scheduled events are displayed in your time zone. Click Next to proceed.
   4. For Custom event data, provide data to include in the body of your event message. You can specify the message as plain text or in Base64 format. For this example, specify the text, hello stranger as the body of the event message. If the message is in Base64 format, you can choose to have the message decoded when the event is sent. You can also specify the content type for your custom event data. Click Next to proceed.
   5. For Event consumer, specify the application or job to receive events. Notice that you can choose from a list of defined applications and jobs. For this example, use the myapp application that references the icr.io/codeengine/cron image. If you have not yet created your app or job, you can specify the name of your application or job and create your application or create your job after you create the Periodic timer subscription. For applications only, you can optionally specify a path. By default, events are routed to the root URL of the destination application. You can send events to a different destination within the app by specifying a path. For example, if your subscription path specifies /events, the events are sent to https://<base application URL>/events. Click Next to proceed.
   6. For Summary, review the settings for your Periodic timer event subscription and make changes if needed. When ready, click Create to create the Periodic timer subscription.

5. Now that your Periodic timer subscription is created, go to the Event subscriptions page to view a listing of defined subscription.

6. To update a subscription, navigate to your Periodic timer subscription page. From the Event subscriptions page, click the name of the subscription that you want to update.

7. From your Periodic timer subscription page, change the data in the event message. From the Custom event data tab, change the event data to hello sunshine. Click Save to save your changes.

8. Because the myapp application references the sample cron application, which prints information to log files, you can view the logs. View the application logs for the myapp event consumer application and see that the event message is hello sunshine. See Viewing application logs from the console.

Subscribing to Periodic timer (cron) events for an application with the CLI

Before you begin

• Set up your Code Engine CLI environment.
• Create a project.
• Create an application. For example, create an application that is called myapp that uses the icr.io/codeengine/cron image. This image is built from cron.go, available from the Samples for IBM Cloud Code Engine GitHub repo

ibmcloud ce application create --name myapp --image icr.io/codeengine/cron

To connect your application to the Periodic timer subscription with the CLI, use the ibmcloud ce sub cron create command.

ibmcloud ce sub cron create --name NAME --destination-type APP --destination APPLICATION_NAME --schedule CRON

For example, to create a cron subscription that sends an event to an app called myapp every day at midnight:

ibmcloud ce sub cron create --name mycronevent --destination-type app --destination myapp --schedule '0 0 * * *'

You must wrap the schedule value in quotation marks to ensure that it is treated as a single string.

The following table summarizes the options that are used in the previous example with the sub cron create command. For more information about the command and its options, see the ibmcloud ce subscription cron create command.

Tips for using the sub cron commands

• By default, events are routed to the root URL of the destination application. You can send events to a different destination within the app by using the --path option. For example, if your subscription specifies --path /events, the events are sent to https://<base application URL>/events.
• The size of data for Periodic timer events is limited to a maximum of 4096 bytes. Thus, if you use the --data option or the --data-base64 option, you can send a maximum of 4096 bytes. For more information, see Limits and quotas for Code Engine.
• Cron subscriptions use the UTC time zone by default. You can change the time zone by specifying the --time-zone option with the sub cron create or the sub cron update commands. For valid time zone values, see the TZ database. Note that if you create a subscription by using kubectl and do not specify a time zone, then the UTC time zone is assigned.
• If you have not yet created your app or job event consumer, use the --force option with the sub cron create command to force the create of the cron event subscription. You can specify the name of your application or job and create your application or create your job after you create the cron subscription.

To verify that your cron subscription was successfully created, run the ibmcloud ce sub cron get --name mycronevent command.

Example output

Getting cron source 'mycronevent'...
OK

Name:          mycronevent
ID:            abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name:  myproject
Project ID:    01234567-abcd-abcd-abcd-abcdabcd1111
Age:           2m21s
Created:       2021-03-14T13:37:51-05:00

Destination Type:  app
Destination:       myapp
Schedule:          0 0 * * *
Time Zone:         UTC
Ready:             true

Events:
    Type     Reason            Age        Source                 Messages
    Normal   FinalizerUpdate   12s        pingsource-controller  Updated "mycronevent" finalizers

From this output, you can see that the destination application is myapp, the schedule is 0 0 * * * (every day at midnight), and the Ready state is true.

Updating your cron subscription with the CLI

To update the cron subscription with the CLI, use the ibmcloud ce subscription cron update command. For example, update the mycronevent subscription to change the schedule to sends an event to an app called myapp every 2 minutes.

ibmcloud ce sub cron update --name mycronevent --schedule '*/2 * * * *'

To verify that your cron subscription was successfully updated, run the ibmcloud ce sub cron get --name mycronevent command. The schedule for the subscription is updated.

Example output

Getting cron source 'mycronevent'...
OK

Name:          mycronevent
ID:            abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name:  myproject
Project ID:    01234567-abcd-abcd-abcd-abcdabcd1111
Age:           2m21s
Created:       2021-08-31T16:00:49-04:00

Destination Type:  app
Destination:       myapp
Schedule:          */2 * * * *
Time Zone:         UTC
Ready:             true

Events:
  Type    Reason                       Age               Source                 Messages
  Normal  PingSourceSynchronized       7s (x3 over 13m)  pingsource-controller  PingSource adapter is synchronized

Want to try a tutorial? See Subscribing to Periodic timer (cron) events. Looking for more code examples? Check out the Samples for IBM Cloud Code Engine GitHub repo.

Viewing event information for an application from the console

To view information about your event subscriptions,

1. From the Code Engine Projects page, go to your project.
2. From the Overview page, click Event subscriptions to view a listing of defined subscriptions.

If your application prints information to log files, as the sample cron application does, then view the log files for your event consumer application. See Viewing application logs from the console.

Viewing event information for an application with the CLI

If your application prints information to log files, as the sample cron application does, then view the log files for your event consumer application with the ibmcloud ce app logs CLI command. For example, to view the logs for the application that you created in the previous example,

ibmcloud ce application logs --application myapp

Example output

Getting logs for all instances of application 'myapp'...
OK

myapp-mw25y-1-deployment-8579d868f4-ssfnr/user-container:
Listening on port 8080
2021-04-13 17:22:08 - Received:
URL: /
Header: Accept-Encoding=[gzip]
Header: Ce-Id=[d2faa29c-8088-410f-bb30-416085c52a0b]
Header: Ce-Source=[/apis/v1/namespaces/81fvkfqi3n6/pingsources/mycronevent]
Header: Ce-Specversion=[1.0]
Header: Ce-Time=[2021-04-13T17:22:00.059682656Z]
Header: Ce-Type=[dev.knative.sources.ping]
Header: Content-Length=[0]
Header: Forwarded=[for=172.30.136.209;proto=http, for=172.30.48.203]
Header: K-Proxy-Request=[activator]
Header: Traceparent=[00-b13196fe439b6d7d67f3205b2f655788-e9fee441cd41158c-00]
Header: User-Agent=[Go-http-client/1.1]
Header: X-B3-Sampled=[0]
Header: X-B3-Spanid=[1dd2d76079811204]
Header: X-B3-Traceid=[710b7c383682d0cd1dd2d76079811204]
Header: X-Envoy-Attempt-Count=[1]
Header: X-Envoy-Decorator-Operation=[myapp-mw25y-1.81fvkfqi3n6.svc.cluster.local:80/*]
Header: X-Envoy-Internal=[true]
Header: X-Envoy-Peer-Metadata=[ChQKDkFQUF9DT05UQUlORVJTEgIaAAoaCgpDTFVTVEVSX0lEEgwaCkt1YmVybmV0ZXMKGAoNSVNUSU9fVkVSU0lPThIHGgUxLjkuMQq+AwoGTEFCRUxTErMDKrADCh0KA2FwcBIWGhRpc3Rpby1pbmdyZXNzZ2F0ZXdheQoTCgVjaGFydBIKGghnYXRld2F5cwoUCghoZXJpdGFnZRIIGgZUaWxsZXIKNgopaW5zdGFsbC5vcGVyYXRvci5pc3Rpby5pby9vd25pbmctcmVzb3VyY2USCRoHdW5rbm93bgoZCgVpc3RpbxIQGg5pbmdyZXNzZ2F0ZXdheQoZCgxpc3Rpby5pby9yZXYSCRoHZGVmYXVsdAowChtvcGVyYXRvci5pc3Rpby5pby9jb21wb25lbnQSERoPSW5ncmVzc0dhdGV3YXlzCiAKEXBvZC10ZW1wbGF0ZS1oYXNoEgsaCTU1YjU0N2Y0ZgoSCgdyZWxlYXNlEgcaBWlzdGlvCjkKH3NlcnZpY2UuaXN0aW8uaW8vY2Fub25pY2FsLW5hbWUSFhoUaXN0aW8taW5ncmVzc2dhdGV3YXkKLwojc2VydmljZS5pc3Rpby5pby9jYW5vbmljYWwtcmV2aXNpb24SCBoGbGF0ZXN0CiIKF3NpZGVjYXIuaXN0aW8uaW8vaW5qZWN0EgcaBWZhbHNlChoKB01FU0hfSUQSDxoNY2x1c3Rlci5sb2NhbAouCgROQU1FEiYaJGlzdGlvLWluZ3Jlc3NnYXRld2F5LTU1YjU0N2Y0Zi10aHN4cAobCglOQU1FU1BBQ0USDhoMaXN0aW8tc3lzdGVtCl0KBU9XTkVSElQaUmt1YmVybmV0ZXM6Ly9hcGlzL2FwcHMvdjEvbmFtZXNwYWNlcy9pc3Rpby1zeXN0ZW0vZGVwbG95bWVudHMvaXN0aW8taW5ncmVzc2dhdGV3YXkKFwoRUExBVEZPUk1fTUVUQURBVEESAioACicKDVdPUktMT0FEX05BTUUSFhoUaXN0aW8taW5ncmVzc2dhdGV3YXk=]
Header: X-Envoy-Peer-Metadata-Id=[router~172.30.48.203~istio-ingressgateway-55b547f4f-thsxp.istio-system~istio-system.svc.cluster.local]
Header: X-Forwarded-For=[172.30.136.209, 172.30.48.203, 172.30.167.171]
Header: X-Forwarded-Proto=[http]
Header: X-Request-Id=[fe8d6cec-f0e4-47c2-b9ae-81764cb377bc]

For more information about logging, see Viewing logs.

Looking for more code examples? Check out the Samples for IBM Cloud Code Engine GitHub repo.

Cron header and body information for events delivered to applications

All events that are delivered to applications are received as HTTP POST messages. Events contain certain HTTP headers that help you to quickly determine key bits of information about the events without looking at the body (business logic) of the event. For more information, see the CloudEvents spec.

ce-id: c329ed76-5004-4383-a3cc-c7a9b82e3ac6
ce-source: /apis/v1/namespaces/6b0v3x9xek5/pingsources/mycronevent
ce-specversion: 1.0
ce-time: 2021-02-26T19:19:00.497637287Z
ce-type: dev.knative.sources.ping

Subscribing to Periodic timer (cron) events for a function from the console

You can create and update Periodic timer event subscriptions for a function from the console.

Before you begin

• Create a project.
• Create a function. For example, create a function that is called myfun that uses the following sample inline code:

/**
 * The `main` function is the entry-point into the function.
 * It has one optional argument 'params', which carries all the
 * parameters the function was invoked with.
*/
async function main(params) {

  // add process environment variables
  params.env = process.env

  // print recognizable string to the log
  console.log('Function invocation via cron subscription');

  // log params object, so invocation can be observed in the logs
  console.dir(params);

  // craft a simple HTTP RC 200 response,
  // which also echos the params object
  response = {
    statusCode: 200,
    headers: {
      'Content-Type': 'application/json;charset=utf-8'
    },
    body: params
  };
  return response
}

Complete the following steps to create and update a Periodic timer event subscription for a function from the console.

1. From the Code Engine Projects page, go to your project.

2. From the Overview page, click Event subscriptions.

3. From the Event subscriptions page, click Create to create your subscription.

4. From the Create event subscription page, complete the following steps:

   1. For Event type, select the Periodic timer tile. Click Next.
   2. For General, provide a name for the Periodic timer subscription, for example, myptimer. You can optionally provide event attributes. Note that if the Periodic timer event consumer is an application, event attributes are available as HTTP headers. If the event consumer is a function, event attributes are available as key-value pairs in the __ce_headers property of the params object. Click Next to proceed.
   3. For Schedule, provide information about the timing of the events. The Periodic timer event producer uses standard crontab syntax to specify interval details. Choose your interval from the provided patterns or provide your own custom cron expression, such as 0 0 * * *, which specifies for the event to occur every day at midnight. For this example, select the schedule pattern for every day, every hour, every minute. Notice that the cron expression is generated for you. The day, hour, and minute patterns and the Cron expression are in Coordinated Universal Time (UTC). If you do not specify a schedule, then this event subscription sends an event every minute. A list of upcoming scheduled events is displayed. Notice that these upcoming scheduled events are displayed in your time zone. Click Next to proceed.
   4. For Custom event data, provide data to include in the body of your event message. You can specify the message as plain text or in Base64 format. For this example, specify the text, hello stranger as the body of the event message. If the message is in Base64 format, you can choose to have the message decoded when the event is sent. You can also specify the content type for your custom event data. Click Next to proceed.
   5. For Event consumer, choose component type Function and specify the function to receive events. Notice that you can choose from a list of defined functions. For this example, use the myfun function that uses the sample inline code. If you have not yet created your function, you can specify the name of your function and Creating function workloads with inline code after you create the Periodic timer subscription. Click Next to proceed.
   6. For Summary, review the settings for your Periodic timer event subscription and make changes if needed. When ready, click Create to create the Periodic timer subscription.

5. Now that your Periodic timer subscription is created, go to the Event subscriptions page to view a listing of defined subscription.

6. To update a subscription, navigate to your Periodic timer subscription page. From the Event subscriptions page, click the name of the subscription that you want to update.

7. From your Periodic timer subscription page, change the data in the event message. From the Custom event data tab, change the event data to { "hello": "world" } and choose application/json as the Content Type of custom event data. Click Save to save your changes.

8. Because the myfun function uses the sample inline code, which prints the full params object to log files, you can view the logs to verify that the function was invoked. View the function logs for the myfun event consumer function and see that the params object contains a key-value pair hello: world. You can also see that the body field of the params object contains the Base64 encoded value { "hello": "world" } See Viewing function logs from the console.

Subscribing to Periodic timer (cron) events for a function with the CLI

Before you begin

• Set up your Code Engine CLI environment.
• Create a project.
• Create a function. For example, create a function called myfun that uses the following sample inline code:

/**
 * The `main` function is the entry-point into the function.
 * It has one optional argument 'params', which carries all the
 * parameters the function was invoked with.
*/
async function main(params) {

  // add process environment variables
  params.env = process.env

  // print recognizable string to the log
  console.log('Function invocation via cron subscription');

  // log params object, so invocation can be observed in the logs
  console.dir(params);

  // craft a simple HTTP RC 200 response,
  // which also echos the params object
  response = {
    statusCode: 200,
    headers: {
      'Content-Type': 'application/json;charset=utf-8'
    },
    body: params
  };
  return response
}

Save the code to a file called sample_inline_code.js and create the function using the following command:

ibmcloud ce function create --name myfun --runtime nodejs --inline-code ./sample_inline_code.js

To connect your function to the Periodic timer subscription with the CLI, use the ibmcloud ce sub cron create command:

ibmcloud ce sub cron create --name NAME --destination-type function --destination FUNCTION_NAME --schedule CRON

For example, to create a cron subscription that sends an event to an app called myfun every day at midnight:

ibmcloud ce sub cron create --name mycronevent --destination-type function --destination myfun --schedule '0 0 * * *'

You must wrap the schedule value in quotation marks to ensure that it is treated as a single string.

The following table summarizes the options that are used in the previous example with the sub cron create command. For more information about the command and its options, see the ibmcloud ce subscription cron create command.

Tips for using the sub cron commands

• The size of data for Periodic timer events is limited to a maximum of 4096 bytes. Thus, if you use the --data option or the --data-base64 option, you can send a maximum of 4096 bytes. For more information, see Limits and quotas for Code Engine.
• Cron subscriptions use the UTC time zone by default. You can change the time zone by specifying the --time-zone option with the sub cron create or the sub cron update commands. For valid time zone values, see the TZ database. Note that if you create a subscription by using kubectl and do not specify a time zone, then the UTC time zone is assigned.
• If you have not yet created your app or job event consumer, use the --force option with the sub cron create command to force the create of the cron event subscription. You can specify the name of your function Create a function after you create the cron subscription.

To verify that your cron subscription was successfully created, run the ibmcloud ce sub cron get --name mycronevent command.

Example output

Getting cron event subscription 'mycronevent'...
OK

Name:          mycronevent
ID:            abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name:  myproject
Project ID:    01234567-abcd-abcd-abcd-abcdabcd1111
Age:           2m21s
Created:       2024-03-14T13:37:51-05:00

Destination Type:  function
Destination:       myfun
Schedule:          0 0 * * *
Time Zone:         UTC
Ready:             true

Events:
  Type    Reason                  Age                Source                 Messages
  Normal  FinalizerUpdate         20s                pingsource-controller  Updated "mycronevent" finalizers
  Normal  PingSourceSynchronized  20s                pingsource-controller  PingSource adapter is synchronized

From this output, you can see that the destination function is myfun, the schedule is 0 0 * * * (every day at midnight), and the Ready state is true.

Updating your cron subscription with the CLI

To update the cron subscription with the CLI, use the ibmcloud ce subscription cron update command. For example, update the mycronevent subscription to change the schedule to sends an event to a function called myfun every 2 minutes:

ibmcloud ce sub cron update --name mycronevent --schedule '*/2 * * * *'

To verify that your cron subscription was successfully updated, run the ibmcloud ce sub cron get --name mycronevent command. The schedule for the subscription is updated.

Example output

Getting cron event subscription 'mycronevent'...
OK

Name:          mycronevent
ID:            abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name:  myproject
Project ID:    01234567-abcd-abcd-abcd-abcdabcd1111
Age:           37m41s
Created:       2024-03-14T14:04:51-05:00

Destination Type:  function
Destination:       myfun
Schedule:          */2 * * * *
Time Zone:         UTC
Ready:             true

Events:
  Type    Reason                  Age                Source                 Messages
  Normal  FinalizerUpdate         20s                pingsource-controller  Updated "mycronevent" finalizers
  Normal  PingSourceSynchronized  20s                pingsource-controller  PingSource adapter is synchronized

Want to try a tutorial? See Subscribing to Periodic timer (cron) events. Looking for more code examples? Check out the Samples for IBM Cloud Code Engine GitHub repo.

Viewing event information for a function from the console

To view information about your event subscriptions:

1. From the Code Engine Projects page, go to your project.
2. From the Overview page, click Event subscriptions to view a listing of defined subscriptions.

If your function prints information to log files, as the sample codeengine job does, then view the log files for your function. See Viewing job logs from the console.

Cron header and body information for events delivered to functions

All events that are delivered to functions are received as HTTP POST messages. Events contain certain HTTP headers that help you to quickly determine key bits of information about the events. HTTP headers are stored in the __ce_headers property of the params object the function gets invoked with. For more information, see the CloudEvents spec.

  __ce_headers: {
     "Ce-Id": "b861440f-0e17-44ab-9bab-826da0c9713f",
     "Ce-Source": "/apis/v1/namespaces/7iuw2furi55/pingsources/mycronevent",
     "Ce-Specversion": "1.0",
     "Ce-Time": "2024-06-02T10:56:00.062572905Z",
     "Ce-Type": "dev.knative.sources.ping"
  }

  {
    "__ce_headers": {
        "Ce-Id": "b861440f-0e17-44ab-9bab-826da0c9713f",
        "Ce-Source": "/apis/v1/namespaces/7iuw2furi55/pingsources/mycronevent",
        "Ce-Specversion": "1.0",
        "Ce-Time": "2024-06-02T10:56:00.062572905Z",
        "Ce-Type": "dev.knative.sources.ping",
        "Content-Length": "14",
        "Content-Type": "text/plain"
    },
    "body": "hello stranger"
  }

Subscribing to Periodic timer (cron) events for a job from the console

You can create and update Periodic timer event subscriptions for a job from the console.

Before you begin

• Create a project.
• Create a job. For example, create a job that is called myjob that uses the codeengine image. This image is built from codeengine.go, available from the Samples for IBM Cloud Code Engine GitHub repo.

Complete the following steps to create and update a Periodic timer event subscription for a job from the console.

1. From the Code Engine Projects page, go to your project.

2. From the Overview page, click Event subscriptions.

3. From the Event subscriptions page, click Create to create your subscription.

4. From the Create event subscription page, complete the following steps:

   1. For General, provide a name for the Periodic timer subscription, for example, myptimer2. You can optionally provide event attributes. Note that if the Periodic timer event consumer is an application, event attributes are available as HTTP headers. If the event consumer is a job, event attributes are available as environment variables. Click Next to proceed.
   2. For Schedule, provide information about the timing of the events. The Periodic timer event producer uses standard crontab syntax to specify interval details. Choose your interval from the provided patterns or provide your own custom cron expression, such as 0 0 * * *, which specifies for the event to occur every day at midnight. For this example, select the schedule pattern for every day, every hour, every minute. Notice that the cron expression is generated for you. The day, hour, and minute patterns and the Cron expression are in Coordinated Universal Time (UTC). If you do not specify a schedule, then this event subscription sends an event every minute. A list of upcoming scheduled events is displayed. Notice that these upcoming scheduled events are displayed in your time zone. Click Next to proceed.
   3. For Custom event data, provide data to include in the body of your event message. You can specify the message as plain text or in Base64 format. For this example, specify the text, hello stranger as the body of the event message. If the message is in Base64 format, you can choose to have the message decoded when the event is sent. You can also specify the content type for your custom event data. Click Next to proceed.
   4. For Event consumer, specify the application or job to receive events. Notice that you can choose from a list of defined applications and jobs. For this example, use the myjob job that references the icr.io/codeengine/codeengine image. If you have not yet created your job, you can specify the name of your job and create your job after you create the Periodic timer subscription. Click Next to proceed.
   5. For Summary, review the settings for your Periodic timer event subscription and make changes if needed. When ready, click Create to create the Periodic timer subscription.

5. Now that your Periodic timer subscription is created, go to the Event subscriptions page to view a listing of defined subscription.

6. To update a subscription, navigate to your Periodic timer subscription page. From the Event subscriptions page, click the name of the subscription that you want to update.

7. From your Periodic timer subscription page, change the data in the event message. From the Custom event data tab, change the event data to hello sunshine. Click Save to save your changes.

8. Because the myjob job references the sample codeengine application, which prints information to log files, you can view the logs. View the job logs for the myjob event consumer job and see that the event message is hello sunshine. See Viewing job logs from the console.

Subscribing to Periodic timer (cron) events for a job with the CLI

Before you begin

• Set up your Code Engine CLI environment.
• Create a project.
• Create a job. For example, create a job that is called myjob that uses the icr.io/codeengine/codeengine image. This image is built from codeengine.go, available from the Samples for IBM Cloud Code Engine GitHub repo.

ibmcloud ce job create --name myjob --image icr.io/codeengine/codeengine

To connect your job to the Periodic timer subscription with the CLI by using the ibmcloud ce sub cron create command.

ibmcloud ce sub cron create --name NAME --destination-type job --destination JOB_NAME --schedule CRON

For example, to create a cron subscription that sends an event to a job called myjob every 5 minutes,

ibmcloud ce sub cron create --name mycronevent --destination-type job --destination myjob --schedule '*/5 * * * *' --data '{ "message": "Hello world!" }' --content-type application/json

You must wrap the schedule value in quotation marks to ensure that it is treated as a single string.

The following table summarizes the options that are used with the sub cron create command in this example. For more information about the command and its options, see the ibmcloud ce subscription cron create command.

Tips for using the sub cron commands

• The size of data for Periodic timer events is limited to a maximum of 4096 bytes. Thus, if you use the --data option or the --data-base64 option, you can send a maximum of 4096 bytes. For more information, see Limits and quotas for Code Engine.
• Cron subscriptions use the UTC time zone by default. You can change the time zone by specifying the --time-zone option with the sub cron create or the sub cron update commands. For valid time zone values, see the TZ database. Note that if you create a subscription by using kubectl and do not specify a time zone, then the UTC time zone is assigned.
• If you have not yet created your app or job event consumer, use the --force option with the sub cron create command to force the create of the cron event subscription. You can specify the name of your application or job and create your application or create your job after you create the cron subscription.

To verify that your cron subscription was successfully created, run ibmcloud ce sub cron get --name mycronevent.

Example output

Getting cron source 'mycronevent'...
OK

Name:          mycronevent
ID:            abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name:  myproject
Project ID:    01234567-abcd-abcd-abcd-abcdabcd1111
Age:           54s
Created:       2021-04-13T11:38:50-05:00

Destination Type:  job
Destination:       myjob
Schedule:          */5 * * * *
Time Zone:         UTC
Content Type:      application/json
Data:              { "message": "Hello world!" }
Ready:             true

Events:
    Type     Reason            Age        Source                 Messages
    Normal   FinalizerUpdate   12s        pingsource-controller  Updated "mycronevent" finalizers

From this output, you can see that the destination job is myjob, the schedule is */5 * * * * (every 5 minutes), and the Ready state is true.

Job runs that are created by subscriptions are deleted after 10 minutes.

ibmcloud ce sub cron update --name mycronevent --schedule '*/2 * * * *'

Getting cron source 'mycronevent'...
OK

Name:          mycronevent
ID:            abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name:  myproject
Project ID:    01234567-abcd-abcd-abcd-abcdabcd1111
Age:           2m21s
Created:       2021-08-31T16:00:49-04:00

Destination Type:  job
Destination:       myjob
Schedule:          */2 * * * *
Time Zone:         UTC
Content Type:      application/json
Data:              { "message": "Hello world!" }
Ready:             true

Events:
  Type    Reason                       Age               Source                 Messages
  Normal  PingSourceSynchronized       7s (x3 over 13m)  pingsource-controller  PingSource adapter is synchronized

Viewing event information for a job from the console

To view information about your event subscriptions,

1. From the Code Engine Projects page, go to your project.
2. From the Overview page, click Event subscriptions to view a listing of defined subscriptions.

If your job prints information to log files, as the sample codeengine job does, then view the log files for your event consumer job. See Viewing job logs from the console.

Viewing event information for a job with the CLI

If your job prints information to log files, as the sample codeengine job does, you can find the job run that was created from the Periodic timer (cron) event and then view the job run logs. For example, to find the job run for the job in the previous example,

ibmcloud ce jobrun list

Example output

Listing job runs...
OK

Name         Failed  Pending  Requested  Running  Succeeded  Unknown  Age
myjob-kd829  0       0        0          0        1          0        43s

View the logs for the job run by specifying the job run name.

ibmcloud ce jobrun logs --jobrun myjob-kd829

Example output

Hello from helloworld! I'm a batch job! Index: 0

Hello World from:
. ___  __  ____  ____
./ __)/  \(    \(  __)
( (__(  O )) D ( ) _)
.\___)\__/(____/(____)
.____  __ _   ___  __  __ _  ____
(  __)(  ( \ / __)(  )(  ( \(  __)
.) _) /    /( (_ \ )( /    / ) _)
(____)\_)__) \___/(__)\_)__)(____)

Some Env Vars:
--------------
CE_DATA={ "message": "Hello world!" }
CE_ID=abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
CE_SOURCE=/apis/v1/namespaces/1234abcd1a2/pingsources/mycroneventjob
CE_SPECVERSION=1.0
CE_TIME=2021-04-13T17:41:00.429658447Z
CE_TYPE=dev.knative.sources.ping
CONTENT_TYPE=application/json
HOME=/root
HOSTNAME=myjob-mpps4-0-0
JOB_INDEX=0
KUBERNETES_PORT=tcp://172.21.0.1:443
KUBERNETES_PORT_443_TCP=tcp://172.21.0.1:443
KUBERNETES_PORT_443_TCP_ADDR=172.21.0.1
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_SERVICE_HOST=172.21.0.1
KUBERNETES_SERVICE_PORT=443
KUBERNETES_SERVICE_PORT_HTTPS=443
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
SHLVL=1

Note that log information for job runs lasts for only one hour. For more information about logging, see Viewing logs.

For more information about the environment variables that are sent by cron, see Environment variables for events.

Looking for more code examples? Check out the Samples for IBM Cloud Code Engine GitHub repo.

Environment variables for events that are delivered to jobs

All events that are delivered to a job are received as environment variables. These environment variables include a prefix of CE_ and are based on the CloudEvents spec.

Each event contains some common environment variables that appear every time that the event is delivered to a job. The actual set of variables in each event can include more options. For more information, see the CloudEvent attributes.

The following table describes the environment variables that are specific to cron events.

CE_DATA={ "message": "Hello world!" }
CE_ID=abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
CE_SOURCE=/apis/v1/namespaces/1234abcd1a2/pingsources/mycroneventjob
CE_SPECVERSION=1.0
CE_TIME=2021-04-13T17:41:00.429658447Z
CE_TYPE=dev.knative.sources.ping

Deleting a subscription from the console

1. From the Code Engine Projects page, go to your project.
2. From the Overview page, click Event subscriptions to view a listing of defined subscriptions.
3. From the list of subscriptions, delete the subscription that you want to remove from your application or job.

If you delete an app or a job, the subscription is not deleted.

Deleting a subscription with the CLI

You can delete a subscription by running the ibmcloud ce sub cron delete or the ibmcloud ce sub cos delete command.

For example, delete a cron subscription that is called mycronevent2,

ibmcloud ce subscription cron delete --name mycronevent2

If you delete an app or a job, the subscription is not deleted. Instead, in the CLI, the subscription moves to ready state of false because the subscription depends on the availability of the application or job. If you re-create the app or job (or another app or job with the same name), your subscription reconnects and the Ready state is true.