Hi @Sharma_Shruti - good questions. Please find my answers below.
1. You could use `--since` and `--upto` flags to specify the timestamp, and if there are too many activations, `--limit` and `--skip` would help to traverse the pages. Example: wsk activation list --since 1605609603069 --upto 1605780223069
Please note that, activation TTL is 7 days.
2. Activation logs are generated by the action being executed. If you use console.log in your code, they prints the logs out.
3. As mentioned in point #1, activation TTL (incl. logs) is 7 days. If you need older logs, you could create an automated job to export logs to an external persistence.
4. Adobe Developer Console gives you access to APIs, SDKs and developer tools to build on, integrate, and extend Adobe products.
Project Firefly provides the tools to help debug your serverless apps / Runtime actions (along with a lot more dev convenience). You are invited to try it out.
5. How do you create the cache from the beginning? Where is it stored?
6. Same as #5, what do you mean by "Runtime cache" ?
7. I/O Runtime provides a serverless platform to run your node.js code. What you do in the code depends on specific use cases. If they involves Adobe Stock, then you would write the code interacting with its API. Adobe provides an SDK to make it more convenient to write node.js code with Stock API.