dr_venture

Re: Can the firefly project access AEM Assets api? - Project Firefly

I am not fullu clear on what your requirements are for your use case but yes App Builder/Project Firefly can call the AEM Assets API. This is of course if the AEM instance is hosted on the public internet and the api end point is not protected by a firewall. I have written actions in the past that used the Assets API and it was pretty straight forward to do. Project Firefly/App Builder Actions are built using standard nodejs and nodejs has the fetch library for making POST/GET/PATCH/DELETE Rest ...

141

Re: developer.adobe.com/console - Access denied - Project Firefly

Can you send me a DM with your information and company your working for etc? I can have someone from our side look into it and point you to the right person on our side.

Re: developer.adobe.com/console - Access denied - Project Firefly

Did you follow the instructions found on this web page? https://www.adobe.io/app-builder/docs/overview/getting_access/ Per the page above you need be part of an Enterprise Organization that has Adobe products, and the admin of that Enterprise Organization needs to assign you to the Role of Developer or System Admin to be able to gain access to the developer console.Does that help?

113

Re: 401: request is invalid, reason: failed authorization. Please verify your token and organization id - Project Firefly

That does not seem like the fix though. Now that I think about it more and look at the error closer. Is the caller of that action a part of your org and are they passing AUTH header with the request to make that call?

Re: 401: request is invalid, reason: failed authorization. Please verify your token and organization id - Project Firefly

BTW saw this note in the auth section of the product documentation https://www.adobe.io/app-builder/docs/guides/security/ The validator action enabled by require-adobe-auth: true annotation requires the provided IMS access token to have the read_organizations scope. While it is always the case for user tokens used in SPAs, the JWT access tokens used in headless applicationss may not have this scope. This will be the case if it is generated to integrate with the following services:Adobe Analytics...

Re: 401: request is invalid, reason: failed authorization. Please verify your token and organization id - Project Firefly

Would you mind posting or sending me the code for that action so we can look at it closer?

Re: Adobe Experience Platform Query Service - Adobe Experience Platform

good pointsyou could use firefly and put in an Alarm (cron) job that would refresh the cached dataset independent of the users interactions. The user would never hit the 2min refresh but it would still be there. Not trying to under play the need for fast preformant API's of course. It would be ideal if this caching was not needed at all. I understand the fustration. I don't work in AEP engineering or product management so I dont really know the answer to your question about correct use. I would ...

172

Re: SFTP from project firefly worker - Project Firefly

Well that is one of the reasons we built firefly. To help provide easy extention points for our products. I hope it helps with your use case. Let us know here in the forum if you need more help.

167

Re: SFTP from project firefly worker - Project Firefly

Your decision point, I think, is Event or Alarm based execution. Alarms are like Cron jobs(timer execution)Your deployed Firefly Actions would run in our Adobe cloud, so they should be able to access any publicly available endpoint. Firefly Actions are written in nodejs which has a ton of librarys for calling SFTP endpoints. On the AEM side I would imagine your going to use the Assets API to get and put files. There are also ways to hook into AEM Asset events. I have not done it yet but I know i...

182

Re: SFTP from project firefly worker - Project Firefly

There are no outbound restrictions that I know of. The only limitation I can think of there would be the max Action run time. Serverless Actions (functions) are not long running by design so each Action by default would need to complete in under 1 minute before it would be timed out. This is configurable up to 1,800,000ms per the documentation but 1 min is the default and complies with general serverless principles.https://www.adobe.io/apis/experienceplatform/runtime/docs.html#!adobedocs/adobeio...

187

Re: Adobe Experience Platform Query Service - Adobe Experience Platform

There will always be a small additional call time added when using Firefly actions to access the AEP query service. It is another layer between the client and the data. That being said it should be a small addition when compared to calling query service directly.It depends on your use case but the value added by using Firefly Actions is the ability to use the State and File storage layer to do caching of data. Please see this thread on caching of datahttps://experienceleaguecommunities.adobe.com...

222

Re: @parcel/core - Project Firefly

I added a bug to the engineering project for the aio app plugin in github.https://github.com/adobe/aio-cli-plugin-app/issues/449If you would like to follow the issue or add some notes please feel free to.

227

Re: @parcel/core - Project Firefly

There is a bug. I hit this same issue on widows a couple of weeks back. I had to move my project to C drive to resolve the issue.I will check and see what the bug number is so you can follow its resolution.

228

Re: Action result max size and good practice - Project Firefly

Here is a page with the standard list of limitations around Actions. As you can see 1mb is the max result you can return so you have some limitations about how big your data can grow before you need to do Paging of the result set. If the data you are retrieving from AEP does not to be real-time I would recommend catching the data then giving the users the same result setup until a time period has passed where the data would be too old to be considered useful in the app. For example, if your app ...

149

Re: Bootstrapping already developed App using the CLI - Project Firefly

I think it could do the key gen as well with the right apis in place. Make call to request key, get key and update local .env. I checked with project management and this is not on our radar in the near future. What i suggest is for you to go to the CLI github issues page found here https://github.com/adobe/aio-cli/issues and submit it as a feature request. Post the issue number here when done and I will endorse the idea as well. I think its a great idea.

197

Re: Bootstrapping already developed App using the CLI - Project Firefly

I think it could do the key gen as well with the right apis in place.

200

Re: Bootstrapping already developed App using the CLI - Project Firefly

That would be cool. If i understand you correctly you are saying the cli can inspect the local application and request all the needed services, workspace, etc in the console for you and set it all up. Is that right? If so I think that would be cool. I don't think we are there yet but we could check and see if there is something like this on the radar. It would be a little tricky with key generation and some other items but it's not at all impossible.

230

Re: Announcement: Adobe I/O Runtime: Node 14 Support Added - Project Firefly

{ "presets": [ [ "@babel/preset-env", { "targets": { "node": "current" } } ] ], "plugins": ["@babel/plugin-transform-react-jsx"] }If stock .babelrc then after adding the file contents would look like this ^

268

Re: How To Install Developed Project Firefly For Other Or... - Project Firefly

I have asked around and we have no formal material built to help support multi org distribution. It's on the list for a blog post in the future but I don't think that will help you in the short term. Basically, our guidance at this time is to use CI/CD build pipelines to automate the manual process of deploying to each org.We do have documentation around build automation...Office hours video is found hereDocumentation is here Once you get your project to deploy to one org basically the trick wou...

219

Re: How To Install Developed Project Firefly For Other Or... - Project Firefly

The question of cross org distribution is a good question. The bad news is there is not a super simple turn-key way to do this today. The good news is we have a release in the works for this year that will bring cross org deployment up to that turn-key level. Until that is released you will need to do code deploys from your repo into the target org one by one and follow the standard process. I know it's not the cleanest solution but with some automation workflows like GitHub actions or another b...

266

Re: Announcement: Adobe I/O Runtime: Node 14 Support Added - Project Firefly

Here is a video that you can watch where I update an existing Firefly project to node 14.https://www.youtube.com/watch?v=F-SKT9PxUNw

354

Re: SSL error with Node 12 : TLS Configuration - Project Firefly

Is that TLS issue still persisting for you with node 14?

741

Re: SSL error with Node 12 : TLS Configuration - Project Firefly

In your projects root folder is a file named package.json. in there you need to update the node support from ^10 || ^12 to 12^ || 14^. I will send you a video on how to do it via messaging. The video will be posted to YouTube Adobe Developer channel next week. Cheers

784