Closed m8pple closed 3 years ago
(The actual problem was that I gave it v4 xml, so the syntax error is just because of that. I didn't realise it still wanted v3-ish xml)
Put another way, I guess the question is "How do I re-load (or un-load) the graph-type without restarting the orchestrator?"
Can you please specify the Orchestrator version you were running this on? I have been unable to reproduce this on 1.0.0-alpha
with a broken XML of my own making.
Ah, sorry : missed the revision off this one.
Pretty sure it was some version of development
, as it's the old command syntax, and it's a problem with it not being able to
parse v4 syntax. It's from when I was following the original instructions, before switching to 1.0.0-alpha.
Now 1.0.0-alpha
is the default this doesn't really matter, so I'll close it.
If a graph fails to load (e.g. due to syntax error), then the graph type name is still locked. This means that if you try to fix the syntax error and then reload, it can't be loaded:
Listing the tasks doesn't show the graph (I think because a task is like a graph instance?):
Based on the documented commands in I tried to unload, but didn't manage to find the right approach:
I'm not sure what the intended behaviour is, but as a user I assumed that if the graph failed to load it would not be registered, or that I would be able to over-write it, or be able to see it in the set of graphs.