apify-cli 0.19.3-beta.3 → 0.19.3-beta.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -301,6 +301,9 @@ Commands are designed to be used in Actor runs. All commands are in PoC state, d
301
301
  ```
302
302
  USAGE
303
303
  $ apify actor
304
+
305
+ DESCRIPTION
306
+ Commands are designed to be used in Actor runs. All commands are in PoC state, do not use in production environments.
304
307
  ```
305
308
 
306
309
  _See code: [src/commands/actor/index.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/actor/index.js)_
@@ -312,6 +315,9 @@ Gets the actor input value from the default key-value store associated with the
312
315
  ```
313
316
  USAGE
314
317
  $ apify actor:get-input
318
+
319
+ DESCRIPTION
320
+ Gets the actor input value from the default key-value store associated with the actor run.
315
321
  ```
316
322
 
317
323
  _See code: [src/commands/actor/get-input.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/actor/get-input.js)_
@@ -326,6 +332,9 @@ USAGE
326
332
 
327
333
  ARGUMENTS
328
334
  KEY Key of the record in key-value store
335
+
336
+ DESCRIPTION
337
+ Gets a value from the default key-value store associated with the actor run.
329
338
  ```
330
339
 
331
340
  _See code: [src/commands/actor/get-value.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/actor/get-value.js)_
@@ -342,6 +351,7 @@ ARGUMENTS
342
351
  ITEM JSON string with one object or array of objects containing data to be stored in the default dataset.
343
352
 
344
353
  DESCRIPTION
354
+ Stores an object or an array of objects to the default dataset of the actor run.
345
355
  It is possible to pass data using item argument or stdin.
346
356
  Passing data using argument:
347
357
  $ apify actor:push-data {"foo": "bar"}
@@ -357,21 +367,20 @@ Sets or removes record into the default key-value store associated with the Acto
357
367
 
358
368
  ```
359
369
  USAGE
360
- $ apify actor:set-value KEY [VALUE]
370
+ $ apify actor:set-value KEY [VALUE] [-c <value>]
361
371
 
362
372
  ARGUMENTS
363
373
  KEY Key of the record in key-value store.
364
-
365
374
  VALUE Record data, which can be one of the following values:
366
375
  - If empty, the record in the key-value store is deleted.
367
376
  - If no `contentType` flag is specified, value is expected to be any JSON string value.
368
377
  - If options.contentType is set, value is taken as is.
369
378
 
370
- OPTIONS
371
- -c, --contentType=contentType Specifies a custom MIME content type of the record. By default "application/json" is
372
- used.
379
+ FLAGS
380
+ -c, --contentType=<value> Specifies a custom MIME content type of the record. By default "application/json" is used.
373
381
 
374
382
  DESCRIPTION
383
+ Sets or removes record into the default key-value store associated with the Actor run.
375
384
  It is possible to pass data using argument or stdin.
376
385
  Passing data using argument:
377
386
  $ apify actor:set-value KEY my-value
@@ -387,20 +396,21 @@ Runs a specific actor remotely on the Apify cloud platform.
387
396
 
388
397
  ```
389
398
  USAGE
390
- $ apify call [ACTORID]
399
+ $ apify call [ACTORID] [-b <value>] [-t <value>] [-m <value>] [-w <value>]
391
400
 
392
401
  ARGUMENTS
393
402
  ACTORID Name or ID of the actor to run (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
394
403
  command runs the remote actor specified in the ".actor/actor.json" file.
395
404
 
396
- OPTIONS
397
- -b, --build=build Tag or number of the build to run (e.g. "latest" or "1.2.34").
398
- -m, --memory=memory Amount of memory allocated for the actor run, in megabytes.
399
- -t, --timeout=timeout Timeout for the actor run in seconds. Zero value means there is no timeout.
400
- -w, --wait-for-finish=wait-for-finish Seconds for waiting to run to finish, if no value passed, it waits forever.
405
+ FLAGS
406
+ -b, --build=<value> Tag or number of the build to run (e.g. "latest" or "1.2.34").
407
+ -m, --memory=<value> Amount of memory allocated for the actor run, in megabytes.
408
+ -t, --timeout=<value> Timeout for the actor run in seconds. Zero value means there is no timeout.
409
+ -w, --wait-for-finish=<value> Seconds for waiting to run to finish, if no value passed, it waits forever.
401
410
 
402
411
  DESCRIPTION
403
- The Actor is run under your current Apify account. Therefore you need to be logged in by calling "apify login". It
412
+ Runs a specific actor remotely on the Apify cloud platform.
413
+ The Actor is run under your current Apify account. Therefore you need to be logged in by calling "apify login". It
404
414
  takes input for the Actor from the default local key-value store by default.
405
415
  ```
406
416
 
@@ -412,18 +422,20 @@ Creates a new Actor project directory from a selected boilerplate template.
412
422
 
413
423
  ```
414
424
  USAGE
415
- $ apify create [ACTORNAME]
425
+ $ apify create [ACTORNAME] [-t <value>] [--skip-dependency-install]
416
426
 
417
427
  ARGUMENTS
418
428
  ACTORNAME Name of the Actor and its directory
419
429
 
420
- OPTIONS
421
- -t, --template=template Template for the Actor. If not provided, the command will prompt for it.
430
+ FLAGS
431
+ -t, --template=<value> Template for the Actor. If not provided, the command will prompt for it.
422
432
  Visit
423
433
  https://raw.githubusercontent.com/apify/actor-templates/master/templates/manifest.json to
424
434
  find available template names.
425
-
426
435
  --skip-dependency-install Skip installing Actor dependencies.
436
+
437
+ DESCRIPTION
438
+ Creates a new Actor project directory from a selected boilerplate template.
427
439
  ```
428
440
 
429
441
  _See code: [src/commands/create.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/create.js)_
@@ -437,6 +449,7 @@ USAGE
437
449
  $ apify info
438
450
 
439
451
  DESCRIPTION
452
+ Displays information about the currently active Apify account.
440
453
  The information is printed to the console.
441
454
  ```
442
455
 
@@ -448,17 +461,18 @@ Initializes a new Actor project in an existing directory.
448
461
 
449
462
  ```
450
463
  USAGE
451
- $ apify init [ACTORNAME]
464
+ $ apify init [ACTORNAME] [-y]
452
465
 
453
466
  ARGUMENTS
454
467
  ACTORNAME Name of the Actor. If not provided, you will be prompted for it.
455
468
 
456
- OPTIONS
469
+ FLAGS
457
470
  -y, --yes Automatic yes to prompts; assume "yes" as answer to all prompts. Note that in some cases, the command may
458
471
  still ask for confirmation.
459
472
 
460
473
  DESCRIPTION
461
- The command only creates the ".actor/actor.json" file and the "storage" directory in the current directory, but will
474
+ Initializes a new Actor project in an existing directory.
475
+ The command only creates the ".actor/actor.json" file and the "storage" directory in the current directory, but will
462
476
  not touch anything else.
463
477
 
464
478
  WARNING: The directory at "storage" will be overwritten if it already exists.
@@ -472,13 +486,14 @@ Logs in to your Apify account using a provided API token.
472
486
 
473
487
  ```
474
488
  USAGE
475
- $ apify login
489
+ $ apify login [-t <value>]
476
490
 
477
- OPTIONS
478
- -t, --token=token [Optional] Apify API token
491
+ FLAGS
492
+ -t, --token=<value> [Optional] Apify API token
479
493
 
480
494
  DESCRIPTION
481
- The API token and other account information is stored in the ~/.apify directory, from where it is read by all other
495
+ Logs in to your Apify account using a provided API token.
496
+ The API token and other account information is stored in the ~/.apify directory, from where it is read by all other
482
497
  "apify" commands. To log out, call "apify logout".
483
498
  ```
484
499
 
@@ -493,8 +508,9 @@ USAGE
493
508
  $ apify logout
494
509
 
495
510
  DESCRIPTION
511
+ Logs out of your Apify account.
496
512
  The command deletes the API token and all other account information stored in the ~/.apify directory. To log in again,
497
- call "apify login".
513
+ call "apify login".
498
514
  ```
499
515
 
500
516
  _See code: [src/commands/logout.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/logout.js)_
@@ -505,14 +521,18 @@ Pulls an Actor from the Apify platform to the current directory. If it is define
505
521
 
506
522
  ```
507
523
  USAGE
508
- $ apify pull [ACTORID]
524
+ $ apify pull [ACTORID] [-v <value>]
509
525
 
510
526
  ARGUMENTS
511
527
  ACTORID Name or ID of the actor to run (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
512
528
  command will update the Actor in the current directory based on its name in ".actor/actor.json" file.
513
529
 
514
- OPTIONS
515
- -v, --version=version Actor version number which will be pulled, e.g. 1.2. Default: the highest version
530
+ FLAGS
531
+ -v, --version=<value> Actor version number which will be pulled, e.g. 1.2. Default: the highest version
532
+
533
+ DESCRIPTION
534
+ Pulls an Actor from the Apify platform to the current directory. If it is defined as Git repository, it will be
535
+ cloned. If it is defined as Web IDE, it will fetch the files.
516
536
  ```
517
537
 
518
538
  _See code: [src/commands/pull.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/pull.js)_
@@ -523,31 +543,28 @@ Uploads the actor to the Apify platform and builds it there.
523
543
 
524
544
  ```
525
545
  USAGE
526
- $ apify push [ACTORID]
546
+ $ apify push [ACTORID] [--version-number <value>] [-v <value>] [-b <value>] [-w <value>] [--no-prompt]
527
547
 
528
548
  ARGUMENTS
529
549
  ACTORID Name or ID of the Actor to push (e.g. "apify/hello-world" or "E2jjCZBezvAZnX8Rb"). If not provided, the
530
550
  command will create or modify the actor with the name specified in ".actor/actor.json" file.
531
551
 
532
- OPTIONS
533
- -b, --build-tag=build-tag Build tag to be applied to the successful Actor build. By default, it is taken
534
- from the ".actor/actor.json" file
535
-
536
- -v, --version=version Actor version number to which the files should be pushed. By default, it is
537
- taken from the ".actor/actor.json" file.
538
-
539
- -w, --wait-for-finish=wait-for-finish Seconds for waiting to build to finish, if no value passed, it waits forever.
540
-
541
- --no-prompt Do not prompt for opening the actor details in a browser. This will also not
542
- open the browser automatically.
543
-
544
- --version-number=version-number DEPRECATED: Use flag version instead. Actor version number to which the files
545
- should be pushed. By default, it is taken from the ".actor/actor.json" file.
552
+ FLAGS
553
+ -b, --build-tag=<value> Build tag to be applied to the successful Actor build. By default, it is taken from the
554
+ ".actor/actor.json" file
555
+ -v, --version=<value> Actor version number to which the files should be pushed. By default, it is taken from
556
+ the ".actor/actor.json" file.
557
+ -w, --wait-for-finish=<value> Seconds for waiting to build to finish, if no value passed, it waits forever.
558
+ --no-prompt Do not prompt for opening the actor details in a browser. This will also not open the
559
+ browser automatically.
560
+ --version-number=<value> DEPRECATED: Use flag version instead. Actor version number to which the files should be
561
+ pushed. By default, it is taken from the ".actor/actor.json" file.
546
562
 
547
563
  DESCRIPTION
548
- The Actor settings are read from the ".actor/actor.json" file in the current directory, but they can be overridden
564
+ Uploads the actor to the Apify platform and builds it there.
565
+ The Actor settings are read from the ".actor/actor.json" file in the current directory, but they can be overridden
549
566
  using command-line options.
550
- NOTE: If the source files are smaller than 3 MB then they are uploaded as
567
+ NOTE: If the source files are smaller than 3 MB then they are uploaded as
551
568
  "Multiple source files", otherwise they are uploaded as "Zip file".
552
569
 
553
570
  WARNING: If the target Actor already exists in your Apify account, it will be overwritten!
@@ -561,25 +578,23 @@ Runs the Actor locally in the current directory.
561
578
 
562
579
  ```
563
580
  USAGE
564
- $ apify run
581
+ $ apify run [-p] [--purge-queue] [--purge-dataset] [--purge-key-value-store]
565
582
 
566
- OPTIONS
583
+ FLAGS
567
584
  -p, --purge Shortcut that combines the --purge-queue, --purge-dataset and --purge-key-value-store
568
585
  options.
569
-
570
586
  --purge-dataset Deletes the local directory containing the default dataset before the run starts.
571
-
572
587
  --purge-key-value-store Deletes all records from the default key-value store in the local directory before the run
573
588
  starts, except for the "INPUT" key.
574
-
575
589
  --purge-queue Deletes the local directory containing the default request queue before the run starts.
576
590
 
577
591
  DESCRIPTION
592
+ Runs the Actor locally in the current directory.
578
593
  It sets various APIFY_XYZ environment variables in order to provide a working execution environment for the Actor. For
579
- example, this causes the Actor input, as well as all other data in key-value stores, datasets or request queues to be
580
- stored in the "storage" directory, rather than on the Apify platform.
594
+ example, this causes the Actor input, as well as all other data in key-value stores, datasets or request queues to be
595
+ stored in the "storage" directory, rather than on the Apify platform.
581
596
 
582
- NOTE: You can override the command's default behavior for Node.js actors by overriding the "start" script in the
597
+ NOTE: You can override the command's default behavior for Node.js actors by overriding the "start" script in the
583
598
  package.json file. You can set up your own main file or environment variables by changing it.
584
599
  ```
585
600
 
@@ -594,21 +609,23 @@ USAGE
594
609
  $ apify secrets
595
610
 
596
611
  DESCRIPTION
612
+ Manages secret values for Actor environment variables.
613
+
597
614
  Example:
598
615
  $ apify secrets:add mySecret TopSecretValue123
599
616
 
600
- Now the "mySecret" value can be used in an environment variable defined in ".actor/actor.json" file by adding the "@"
617
+ Now the "mySecret" value can be used in an environment variable defined in ".actor/actor.json" file by adding the "@"
601
618
  prefix:
602
619
 
603
620
  {
604
- "actorSpecification": 1,
605
- "name": "my_actor",
606
- "environmentVariables": { "SECRET_ENV_VAR": "@mySecret" },
607
- "version": "0.1
621
+ "actorSpecification": 1,
622
+ "name": "my_actor",
623
+ "environmentVariables": { "SECRET_ENV_VAR": "@mySecret" },
624
+ "version": "0.1
608
625
  }
609
626
 
610
627
  When the actor is pushed to Apify cloud, the "SECRET_ENV_VAR" and its value is stored as a secret environment variable
611
- of the actor.
628
+ of the actor.
612
629
  ```
613
630
 
614
631
  _See code: [src/commands/secrets/index.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/secrets/index.js)_
@@ -626,6 +643,7 @@ ARGUMENTS
626
643
  VALUE Value of the secret
627
644
 
628
645
  DESCRIPTION
646
+ Adds a new secret value.
629
647
  The secrets are stored to a file at ~/.apify
630
648
  ```
631
649
 
@@ -641,6 +659,9 @@ USAGE
641
659
 
642
660
  ARGUMENTS
643
661
  NAME Name of the secret
662
+
663
+ DESCRIPTION
664
+ Removes the secret.
644
665
  ```
645
666
 
646
667
  _See code: [src/commands/secrets/rm.js](https://github.com/apify/apify-cli/blob/v0.19.3/src/commands/secrets/rm.js)_
@@ -657,6 +678,7 @@ ARGUMENTS
657
678
  PATH Optional path to your INPUT_SCHEMA.json file. If not provided ./INPUT_SCHEMA.json is used.
658
679
 
659
680
  DESCRIPTION
681
+ Validates input schema and prints errors found.
660
682
  The input schema for the Actor is used from these locations in order of preference.
661
683
  The first one found is validated as it would be the one used on the Apify platform.
662
684
  1. Directly embedded object in ".actor/actor.json" under 'input' key
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "apify-cli",
3
- "version": "0.19.3-beta.3",
3
+ "version": "0.19.3-beta.4",
4
4
  "description": "Apify command-line interface helps you create, develop, build and run Apify actors, and manage the Apify cloud platform.",
5
5
  "main": "index.js",
6
6
  "scripts": {
@@ -60,6 +60,7 @@
60
60
  "@crawlee/memory-storage": "^3.5.8",
61
61
  "@oclif/command": "^1.8.36",
62
62
  "@oclif/config": "^1.18.17",
63
+ "@oclif/core": "^2.15.0",
63
64
  "@oclif/errors": "^1.3.6",
64
65
  "@oclif/plugin-commands": "^2.1.0",
65
66
  "@oclif/plugin-help": "^5.1.12",
@@ -109,6 +110,7 @@
109
110
  "init": [
110
111
  "./src/hooks/init"
111
112
  ]
112
- }
113
+ },
114
+ "helpClass": "./src/lib/apify-oclif-help"
113
115
  }
114
116
  }
@@ -0,0 +1,23 @@
1
+ const { Help } = require('@oclif/core');
2
+
3
+ /**
4
+ * Custom help class that overrides how oclif renders help screens.
5
+ *
6
+ * It is registered through package.json.
7
+ *
8
+ * Refer to the oclif documentation for more information:
9
+ * https://oclif.io/docs/help_classes/#custom-help
10
+ *
11
+ * Note: The CLI was crashing when printing help with the latest oclif packages. Be careful when upgrading.
12
+ */
13
+ module.exports = class ApifyOclifHelp extends Help {
14
+ showRootHelp() {
15
+ super.showRootHelp();
16
+
17
+ this.log(this.section(
18
+ 'TROUBLESHOOTING',
19
+ this.wrap(
20
+ 'For general support, reach out to us at https://apify.com/contact\n\n'
21
+ + 'If you believe you are encountering a bug, file it at https://github.com/apify/apify-cli/issues/new')));
22
+ }
23
+ };