Tihomir Surdilovic
Tihomir Surdilovic
It's also mentioned in spec documentation in this section: https://github.com/serverlessworkflow/specification/blob/main/specification.md#workflow-versioning
I'm all for it. small change and would bring imo good value for portability
Yes, i wish we did this to begin with. Will update
agree but much harder to define cleanly in json schema :) looking into it to see if there is nice way
imo the aggregation should happen on runtime side. having an uri is enough for me. i rather not add this is possible, so sorry
"functions": "htttp/mycomp.org/my/prod/function/definitions?namespace=abc" this uri endpoint can aggregate all your function defs and stick in the functions array which then is also validatable against our single functions schema
this is a compile time resolve so yes you can validate its response json, otherwise implement the validation on service side that returns the resolved json, thats fine too since...
what we did this for (ability to use uri) is for **runtimes** to be able to provide function definitions out of the box to users. in case where your users...
these types of requests where its more about runtime user support and not the spec itself are things that all i can say is "deal with it", again sry.
put it inline in the definition then. i honestly dont see anything that we can do except add some "improvements" that again wont work for everyone. so uri is uri