I have custom vars which I want to have access to in all actions. means any other solution than manually add them to all action params in the manifest.yml and the access the custom vars within the action.

is there an option to access the results from the CORE logger from within an action? Basically access the data which can be fetched from console using "aio rt activation list/get" but within an action. Idea is to have an UI which displays the log results.Currently I have written my own logger which ...

@duypnguyen here are some screenshots from my current app development:1) see all files within aio-lib-files with option to see/edit the content as well as delete files (download-option will follow)2) screenshot to edit the file content 

currently I have built both UI and actions to manage all aio-lib-files (read/edit/delete files from UI - let me know if you want a screenshot). and I would love to have something similar for states - just to see what values I have from the UI, maybe change the data ...

is there a function to retrieve all variables set in aio-lib-state? something like the function "list()" from aio-lib-files...

I tried the function "list('/')" as discribed on github to fetch all files https://github.com/adobe/aio-lib-files#usehowever, there were no results (even Inhave some files saved). after a test I think there souldn't be a "/" as parameter, means just call "list.('')". is this a bug in the github desc...

I have some .env variables I want to pass to all actions. Until now, I added the variables in question as params to all actions in the manifest.yml file. but too often I changed something and forgotten to change the manifest as well.question: is there a way to have "real env variables", without addi...

@duypnguyenthanks a lot for the hint! I finally found out what was made me think something has broken: the console entries for 'aio app run --local' have changed (they look now very simialar to aio app deploy). using the --verbose shows some of the old console entries (and a lot more). Here are just...

what is really strange: I made another test as written in my steps - no more error. so if this can't be reproduced, I must have made an error somewhere else ...

@SarahXu here are the updates I made on npm packages:"aio version" => "@adobe/aio-cli/3.7.0 win32-x64 node-v12.16.2" I made another test and I think this is how you can deproduce the problem:1) create an app with a trigger, eg. "alarms/interval" set to 5 min2) run "aio app deploy" and check with "ai...