@runlot/api 0.1.0-rc.102 → 0.1.0-rc.103

package/dist/schema.d.ts

@@ -5077,6 +5077,13 @@ export interface components {
              * @example *\/2 * * * *
              */
             cron: string;
+            /**
+             * @description The name the live deployment gives this expression in `triggers.names`. Absent
+             *     when it has none. It is the current name, so renaming a schedule relabels its
+             *     past runs too.
+             * @example nightly recompute
+             */
+            name?: string;
             /**
              * Format: date-time
              * @description The time the expression named, and the value your handler receives as
@@ -5116,6 +5123,11 @@ export interface components {
         CronSchedule: {
             /** @example 30 18 * * * */
             cron: string;
+            /**
+             * @description The name from `triggers.names`, when the live deployment gives one.
+             * @example nightly recompute
+             */
+            name?: string;
             /**
              * Format: date-time
              * @description When this schedule fires next. Absent when the expression can never fire again;
@@ -5856,6 +5868,17 @@ export interface components {
              *     ]
              */
             crons?: string[];
+            /**
+             * @description A name for each schedule, keyed by its expression, shown in the dashboard and in
+             *     `runlot cron`. Optional and per expression. Every key must be one of `crons`;
+             *     a name is one line of at most 80 bytes.
+             * @example {
+             *       "30 18 * * *": "nightly recompute"
+             *     }
+             */
+            names?: {
+                [key: string]: string;
+            };
         };
         /**
          * @description Queues. Two lists. A project may produce into a queue it does not consume, and