Hello,The solution is to create an action that acts as an endpoint for
reading data from the other application. Our security model assumes that
each application owns its data. If it needs to share data with another
application, it can use custom events or expose an endpoint. Thank
Hello there, We have on our roadmap to add support for user access
control in the Admin Console. Until then, we only support out of the box
the use case where the user has access to the data in the first place.
Hello Abhinav, Did you create a Runtime namespace in the Developer
Console - https://console.adobe.io ? If yes, then from the Console
project overview page you can download the project configuration file
and you will find the credential needed. Cheers,Mihai
Project Firefly is not a generic framework for creating cloud native
apps. It is a framework that is designed from ground-up to support
3rd-parties who want to extend and integrate Adobe Experience Cloud and
Adobe Experience Platform. It is pre-integrated with Adobe APIs, Events,
Adobe I/O Runtime, and Adobe authentication/authorization. Our value
proposition is that Project Firefly is the fastest and easiest way for a
developer to extend and integrate with Adobe enterprise solutions.
You can apply for access on [Adobe’s Prelease
forum](http://www.adobeprerelease.com) -> Project Firefly -> Apply. The
following information is needed:Your Adobe Organization ID and
Organization Name. We are granting access to organizations, not to
individuals. You can retrieve your Organization ID and Name from Adobe
Admin Console, the ID is part of the URL (something like
some_hash@AdobeOrg) and the Name is displayed in the top-right
corner.Describe your use case. For example: “I want to extend...
Project Firefly is available starting on May 18, 2020. We invite Adobe
enterprise customers and partners to join our Developer Preview release.
We will announce the General Availability release at a later time.
Project Firefly is a complete design, application, and runtime framework
for building 3rd-party cloud native applications. These custom web apps
run on Adobe infrastructure and extend the functionality of Adobe
Experience Platform and Adobe Experience Cloud. With Project Firefly,
customers can build custom integrations between Adobe products and
3rd-party products, enabling greater efficiency and improved workflows.
Check the project home page for more information.
Hello, Two things come to my mind:1. Do you have logs in action 2? do
you have some try catch that return an error object?2. I suspect that
action 2 is set to run concurrently in the same container. Tweak the
concurrency value to 100 and see if this happens again
Hello Sharma, I believe there is a thread open on the same topic with
the customer support. Without knowing your code and what you see in your
logs, here are some pointers:1. We have customers in production with AEM
Commerce and I/O Runtime and there were no issues reported2. While
working with these customers in pre-production, the latency or time-out
problems were always related to the downstream service (the Commerce
platform). For example, rate limiting or slow response. You should be
Hello there, Adobe I/O Runtime is the Adobe's serverless platform that
is designed to support 3rd-parties who want to extend Adobe enterprise
solutions. For the past 2 years we've been building capabilities to make
it as easier as possible. An example if Project Firefly -
https://github.com/AdobeDocs/project-firefly.Learning to use I/O Runtime
and Project Firefly ensures that you can use the same mechanism to
extend Adobe Experience Cloud and Adobe Experience Platform, while
reusing all the tool...
Hello there, In two weeks from now (week of April 26th, 2020) we will
update the way I/O Runtime handles activations for successful blocking
invocations.This is the new behavior:By default, successful blocking
invocations will not produce an activation record, thus running “wsk
activation list” will not list any of these. Logs are still recorded and
can be retrieved using the activation ID - this is still being sent to
the client invoking the actionBlocking invocations that failed will
Hello there, Your error is expected as you've got access to I/O Runtime
through custom namespaces. This doesn't give you access to I/O Runtime
through the Developer Console. We will be revisiting the way we
onboarded customers and re-onboard them through the Developer Console.
Expect this to be done in May, 2020.
We've updated the docs to highlight that if you have dependencies, then
you have to point to the folder where the action is defined and the
action has to be defined in a file called index.js
Hello there, Can you try using wsk for deploying your ZIP? There is
another way of deploying a ZIP action using the wsk command. You miss
the manifest.yaml file flexibility with this mode; you can’t define
multiple actions/packages at the same time. The ZIP file has to have in
the root the package.json file.wsk action create my-action --kind
Hello Alexis, Luckily, I/O Runtime is built on top of an open source
project, Apache OpenWhisk. There are a ton more of resources out there
that go in great details. I noted this request, and when time permits we
will add a more detailed docs on creating RESTful APIs. Regarding Cache
Control, you can find an example here:
Doing a redirect, would be as simple as the example...
Hi Rajneesh, This flow is enabled only for customers who have acquired
the Runtime add-on SKU - this unlocks support for Runtime in I/O
Console. If you have received namespaces from our team, then you will
need to follow the docs and look for the section that points to how to
configure the CLI using the .wskprops file (this is what we gave you).
I just checked in and thinking to take a nap I will look for you guys
after I get some sleepCheers,Mihai Corlan | Developer Evangelist | Adobe
SystemsBlog: http://corlan.org Twitter:
http://twitter.com/mcorlan Mobile: +40 731 498 764