@duypnguyenthere are currently 2 use cases on our list:user can register
to certain tasks in the UI. as soon as an action runs and triggers a
defined event, an email should be sent to the end userin certain cases I
want to send an email to the admin letting him know that the action
failed. the admin is either hard coded or set by UI using
aio-lib-statein both cases the users/emails are registered users within
the experience cloud (they all have either an AdobeID or a FederatedID).
means I could ...
@duypnguyen I will mark the question as answered, thanks gor the help.
for my apps I have written a custom logger - basically writing the most
important mesaages to aio-lib-files. this way, I can habe a custom
screen showing all messages in my logger...
hi @duypnguyen is there a way to see the logs directly in console when
using "aio app run" (similar to "--local")? what I would love to see is
running the app and in the console I can see the debug logs (as in the
screenshot above when using "--local"). sending curl request seems too
since my latest update I can't see any logs of my actions - but they are
working as expected in local environment. I hope I can provide enough
information so somebody might see what I'm doing wrong ...1) local
environment, running "aio app run --local" and invoking an action shows
me some log entries as expected:2) with no changes at all I then
executed "aio app run" (no errors) and invoking the exact same action
(with success in the UI), nothing happens in the logs. I checked the
list with "aio...
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 stores some basic debug information within a file in
aio-lib-files but it would be more flexibel and future-proof if I could
access the CORE logger directly.Here is a screenshot from my own logger
@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 ...
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 description?
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 adding them to all actions? I tried to use env vars
starting with "__OW_" but that was not a success...any hints hiw to do
@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 some of the entries now hidden in --verbose:The
main problem I see in 'aio app run --local' (without --verbose) is he
fact that it takes a long time until the first entry appears. It would
be great i...
@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 "aio rt trigger list" that the trigger has been set3) remove
the trigger from "manifest.yml" (since it does not work on local dev)4)
run "aio app run --local" and check again the "aio rt trigger list" =>...
I just realized a strange behaviour - let's assume the problem is
sitting in front of the desktop ...nevertheless, maybe someone else has
the same issue. What happened? I just upgraded npm packages and aio to
latest versions and tried the "aio app run --local" as usual. What I see
looks as if there is some deployment similar to "aio app deploy" for
some of the files, especially the "manifest.yml". not only takes it a
lot longer to build my local files, it also looks quite different than
maybe I missed a point, but how is it intended to move from a "dev"
workspace to "staging" and later "production"? assume I have a local
directory with all my files and working in a dev environment, what are
the next steps?I assume that I just change the "aio env" by running "aio
app use " and then deploy the app.is this the
right way to do it?