Skip to content

Releases: adobe/aio-cli-plugin-app

5.2.1

24 Nov 03:51
Compare
Choose a tag to compare

5.2.0

23 Nov 17:58
Compare
Choose a tag to compare
  • make serve flag experimental 422349b
  • fix: cannot deploy app to remote via aio app run, it's always local (#329) 7fdd3b4
  • fix: add logging to file for openwhisk-standalone.jar (#325) d49784a
  • fix: https://localhost:9080 404 Not Found in aio app run (#324) e339e57
  • Customisations and Enhancements (#320) 9f5250d
  • fix: ACNA-885 - aio app run's auto-logger shows last action log for last activation even before the command was run (#323) 5221439

5.1.1...5.2.0

5.1.2

20 Nov 08:48
Compare
Choose a tag to compare

fixes: Windows Docker local debugging, app hooks command chaining, app run --local cleanup

10 Nov 03:50
Compare
Choose a tag to compare

NOTES

  1. for app hooks that use @adobe/aio-run-detached please use at least version 1.3.2 and see the section Shell Operators Must Be Quoted in the README.
  2. The openwhisk-standalone.jar that is downloaded for local debugging is versioned, and put in a separate location outside of the app plugin, so you will not have to re-download the .jar again if the app plugin is updated, or the cli is updated.

5.1.0...5.1.1

feat: support for app hook long-running processes via aio-run-detached

26 Oct 14:54
Compare
Choose a tag to compare
  • ACNA-858 - support for app hook long-running processes via aio-run-detached (#301) db51485

5.0.2...5.1.0

Usage

You will need to add @adobe/aio-run-detached as a dependency in your project:

npm install @adobe/aio-run-detached

For example, if you have a long running command called long-running-process.sh, and you want to run it in the pre-app-run app hook, you prefix your command with aio-run-detached like so in your app's package.json:

{
  "scripts": {
    "pre-app-run": "aio-run-detached long-running-process.sh"
  }
}

aio-run-detached will report back to the App plugin the process id of the detached process, so that the App plugin can terminate the detached process when the App plugin command exits.

Logging

Since it is a detached process, logs from stdout and stderr are not available in the terminal. Instead, the logs are written out to disk.

For example:

{
  "scripts": {
    "pre-app-run": "aio-run-detached long-running-process.sh"
  }
}

Log file name format: {processname}.out.log and {processname}.err.log.

In this example, your stdout log will be called long-running-process.sh.out.log and
your stderr log will be called long-running-process.sh.err.log.

Both files will be appended to, and will be created if they don't exist, and both will be created inside a logs folder in your current working folder. Make sure you put your logs folder in your .gitignore in case there are secrets being logged. Newly generated templates will have this folder added in .gitignore.

On every run, a timestamp is logged to the log file to differentiate runs.

5.0.0

19 Oct 16:45
Compare
Choose a tag to compare

aio app logs used to return logs from all actions in the current namespace.
Now it looks for manifest.yml and returns logs for only the actions defined in the manifest.yml and throws an error if there is no manifest.
This is in true sense of app. To see logs from other actions (not defined in the manifest), use aio rt logs.

  • Update docs for logs cmd 0e76410
  • Update lib-runtime (#308) f0ed690
  • New manifest and action level logs with new strip and tail options (#303) e57e2f1

4.1.1...5.0.0

4.1.1

15 Oct 17:02
Compare
Choose a tag to compare

4.1.0...4.1.1

4.1.0

13 Oct 18:07
Compare
Choose a tag to compare

4.0.2...4.1.0

4.0.2

05 Oct 14:36
Compare
Choose a tag to compare
  • delete console.json after generation in init and use (#302) 8cfe58a

4.0.1...4.0.2

fix: use services from imported config if present

28 Sep 14:49
Compare
Choose a tag to compare
  • fix: use services from imported config if present (#290) 9d5f824

4.0.0...4.0.1