This message was deleted.

I just saw the PR 🙂 I haven’t used this resource before but I did leave a comment just now on the GH ticket in case @crooked-holiday-65877 knows more

Morning, I’ve just commented on the issue. I should get some time to have a look later on this evening. I think we should be able to work out how many transitions occur within the definition. As appose to providing this detail in the usage file. But it may get complex so maybe the usage file is a good starting point. I’ll look at the PR later if that’s ok.

Thanks @crooked-holiday-65877! @bulky-florist-87783 maybe we can merge the existing PR once this bit is done. A new GH issue+PR could be made for the iteration Rob mentions?

sure @white-airport-8778 working on it

I don’t think I’ve got much more to add @white-airport-8778 your comments represent some of the things I think are maybe missing. Specifically around the express workflows. There’s a function

calculateRequests

which could possibly be used to calculate the memory consumed & requests.

calculateGBSeconds

perhaps could be changed to support some elements of this too as the calculation looks to be similar looking at the AWS pricing examples. The transition count within a

standard workflow

maybe a little too complex to generate dynamically given the nature of the state machine logic & maybe one for another day. A simple calculation could be to count the total transitions and report that within the estimate.

thanks @crooked-holiday-65877 saved my time