Live vs Non-Live CloudScript Revisions

Question

question

daniel-5 asked Nov 24, '20

Live vs Non-Live CloudScript Revisions

Is there a difference between Live vs 'Non-Live'/TargetedVersions of CloudScript, in particular with regards to how PlayFab provision resources for running these scrips in live loads? Or is 'Live' more of a semantic?

I am considering mapping different versions of CloudScript to my application's version, so as to ensure that the client only access CloudScripts that it is compatible with (with the proper signatures), thereby effectively isolating signature / API changes to each app version.

Much thanks!

CloudScript

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2020-11-25T05:09:59Z

Seth Du answered Nov 25, '20

Live revision will be the default choice when an API is called and features in Automation, including Rules, Scheduled task, are not allowed to specify other revisions.

Thus, you are free to use any revisions that have uploaded to PlayFab via API calls. For example, in the request of ExecuteCloudScript API, you may specify the revision via RevisionSelection property, then assign the value for SpecificRevision property.

2

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

daniel-5 commented · Nov 25, 2020 at 05:02 PM

Thanks @SethDu. So in terms of provisioning resources for load handling - there is no difference between using Live vs SpecificRevisions of CloudScript?

0 ·

Seth Du ♦ daniel-5 commented · Nov 26, 2020 at 03:21 AM

Cloud Script/Azure Function meters computing time with ram consumption (Execution Time in GB-s) and times. Hence, the revisions should have weak correlation.

0 ·

question