@harpreet_ahluwa I setup a new app in a new folder with latest codes, could see the sidebar. then I copied the needed code parts to my current project which is running on CLI 3.7.0

@duypnguyen I changed my code to use the updated aio-lib-ims and it works as expected. thanks for the update!

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 <mydesiredw...

Hi @duypnguyen thanks for the update! I will give it a try later today ...

HI @duypnguyen / @harpreet_ahluwa I made a test yesterday and was able to run `npm install -g @adobe/aio-cli` then `aio app init <myAppName>` including the new layout with the router. there was no need to install any preview version, just updating to latest aio-cli...

@duypnguyen thanks for sharing the "whisk-password" option, great to know!

in your manifest.yaml change action to "require-adobe-auth: false" (key maybe different). with this setup everybody can call the action without access token. you could add your own param to check... would not do it this way due to security, but you could...

I would create a service account for your external tool. basically the external tool fetches a new access token (bearer token) before calling the firefly action. read more about service accounts here: https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/JWT/JWT.md

I see a strange error when changing my triggers/rules using whisk alarms/interval. Example: I had a fully running action (interval 5 mins) and wanted to change the interval. after "aio app undeploy" I changed just the "interval" and deployed again, running into issues (see screenshot). then I played...

I just run an "aio app undeploy" after changing the manifest.yaml and had the following error:maybe it tries to "undeploy" the items according to the new values in the manifest.yaml but not what has been deployed? don't know what problems that might cause - I assume that if all alarm-triggers, rules...