Releases: adobe/aio-cli-plugin-app
5.2.1
- lock [email protected] 1ac239e
- also See 5.2.0 Release Notes
5.2.0
- 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.2
fixes: Windows Docker local debugging, app hooks command chaining, app run --local cleanup
- fix: ACNA-942 - Windows: docker not found when running
aio app run --local --verbose
(openwhisk) (#318) 7b1e73a - fix: ACNA-949 - command chaining, and separators broken (#321) 0b45ddb
- fix: ACNA-882 - Rewriting files during app run is error prone, and leads to unexpected issues (#309) 6c7f62d
- fix: re-enable Github Action, remove Travis CI (#316) b162964 ef6c2a3 5928498 86d7a08 d30d6db d5f4034 060a720 07b63ae
NOTES
- 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. - 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.
feat: support for app hook long-running processes via aio-run-detached
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
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
.