[Beta] Open Cloud Engine API for Executing Luau

[NinjaFurfante07 (iKingNinja)]

Are we going to get an OAuth2 scope for this?

[RuizuKun_Dev (Kitsune)]

@DevelopmentDeadline

You poll for the operation status, and upon completion, receive the script’s return values and logs.

would i be able to use websocket for this?

if no will this ever support websocket?

@DevelopmentDeadline

Access to some cloud service APIs (like DataStores, HttpService, etc.) is disabled to prevent accidental overwriting of production data.

Need a way to determine running in cloud environment and a way to determine if a service is available in cloud environment

---

The script runs in Server context only right?

[unmiss (Jack)]

I’m using this API to bootstrap TestEZ tests in my game. How do I determine if I’m currently in a testing environment? For example, I want to use a mock datastore in my tests instead of DataStoreService, because it’s not supported.

RunService won’t provide any useful information (IsStudio() returns false, but that’s probably expected.)

@DevelopmentDeadline

[NotAstrain]

This might be janky, but I just put this at the top of the source I was sending:
workspace:SetAttribute("IS_AUTO_TEST_ENVIRONMENT", true)

[Dekkonot]

I’m finding the docs rather confusing; if not for the example scripts provided, I’m not sure I’d actually know how to use this.

I can’t really give a specific example of what’s wrong with them beyond saying that it’s really not clear what the actual format of requests are and what the results are. I… assume that LuauExecutionSessionTask is the request format and then it’s reused for the result, but with the fields that are marked as “Output Only” included? If this is the case, why would it not be documented as two distinct structs? It feels like an implementation detail being leaked to users.

Some clarification would be helpful!

[Dekkonot]

Something I’ve noticed is that the LuauExecutionSessionTaskLog seems to not differentiate between the types of output that can exist.

You can run code like this, which should put 4 different types of text in the Output:

local TestService = game:GetService("TestService")
TestService:Message("test blue")
warn("test yellow")
TestService:Error("test red")
print("test normal")

However, they’re all indistinguishable from one another when retrieved with the OpenCloud Luau Execution Task Logs endpoint (quite a mouthful). Is this something that can change?

It’d be cool if I could e.g. omit warnings from the output.

[icemountainrbx]

@Dekkonot

I… assume that LuauExecutionSessionTask is the request format and then it’s reused for the result, but with the fields that are marked as “Output Only” included?

That is correct.

@Dekkonot

If this is the case, why would it not be documented as two distinct structs? It feels like an implementation detail being leaked to users.

Thanks for the feedback! I’ll take this back to the team and see how we can make the docs clearer.

[icemountainrbx]

@Dekkonot

Something I’ve noticed is that the LuauExecutionSessionTaskLog seems to not differentiate between the types of output that can exist.

You can run code like this, which should put 4 different types of text in the Output:

local TestService = game:GetService("TestService")
TestService:Message("test blue")
warn("test yellow")
TestService:Error("test red")
print("test normal")

However, they’re all indistinguishable from one another when retrieved with the OpenCloud Luau Execution Task Logs endpoint (quite a mouthful). Is this something that can change?

It’d be cool if I could e.g. omit warnings from the output.

Thanks for reporting this. Having the MessageType in the log output definitely makes a lot of sense. We are going to work on adding it.