I’d like to know if there’s any way to access the Forge Storage from outside, for example from an AWS Lambda.
I’ve tried the Web Trigger functionality, but the url where the trigger can be called is generated, and can only be generated from within Forge.
We need to know where to access the Storage when a scheduled job starts outside of Forge, therefore we’d have to store this url somewhere else. Using another storage to store the location of the actual storage kinda defeats the purpose of using this system at all… Not to speak about the severe quota limitations.
My question is:
- Is there any other way to access the Storage API externally?
- What are the plans with Forge Storage going forward, can we expect better functionality than a plain key-value store? The current implementation seems more like a proof-of-concept or a tech-demo, than a solution for real-world scenarios.